Xcode Build Perfect Failure -- Copenssl Not Found

Xcode build Perfect failure -- COpenSSL not found

You need to add the following line to your project's (not target) "Library Search Paths" setting: "$(PROJECT_DIR)/**" (including quotes).

Unfortunately, as for now, you need to do that each time you add a depedency and regenerate project as a result.

Error Setting up PerfectlySoft Swift on OS X

Please, use DEVELOPMENT Snapshot instead a release version of Swift:
Swift Snapshot

Perfect Asistant: Build Linux failed due to module cache path on linux vs macOS

In Perfect Assistant project editor window, press and hold button "Build" and choose "Clean Project", then try building it once more.

Alternatively, press and hold button "Open" then choose "Open Terminal", and run commands below:

$ rm -rf .build*
$ rm -rf *.pins
$ rm -rf *.resolved

Then try building.

If you still couldn't understand what was going on, try opening a terminal window and run scripts below:

$ cd "/Users/hange/Developer/RayWenderlich/Practices/ServerSide_Perfect/hello-perfect-assistant"
$ rm -rf .build*
$ rm -rf *.pins
$ rm -rf *.resolved

Which should perform the same task as the second solution.

How to add OpenSSL to an Xcode project

You will need to compile and link it yourself, and your app needs to ship it. If the license of your app and OpenSSL's license are compatible, you may use static linking. Otherwise you will need to dynamically link it.

There are a few documents describing the process and build scripts that you can find with Google searches. For iOS, there's even a Github project. I didn't copy the contents of those documents here since it's too much and it's a moving target.

You can also install OpenSSL with Homebrew. If you just want to have your app run on your Mac and you don't want to distribute it, this is the easiest way: you just need to link it. But if you want to distribute your app, you would need to copy the library/libraries to your app bundle and make sure the the linker finds it there. This also has the disadvantage that there's a possible "disconnect" between your app and the OpenSSL version: if in one year, you update OpenSSL with Homebrew and want to compile/link an older version of your app against the very same OpenSSL version as you've used at that time, you have a problem.

Non-modular headers of OpenSSL library when using modulemap for Swift framework

In the end I couldn't find any better solution than listing all necessary headers into module map and rewriting include macros of the SSL library files from <> syntax to just plain include. I used this little shell script to help me with that:

sed -E -i '' 's/#[[:space:]]*include <openssl\/(.*).h>/#include \"\1\.h"/' $SCRIPT_DIR/../Libraries/openssl/include/openssl/*.h

Swift Package Manager not resolving

So I managed to resolve this and thought it might be useful for others.

I had made my version tag in git as 'v0.1' whereas I needed to give it full semantic versioning e.g 0.1.0 as the tag and that worked succesfully

Openssl (OS X Yosemite) Installation Make Errors

I'm not sure what your problem is. Using XCode 6 (6.1.1, I believe) on Yosemite 10.10.1, I was able to get openssl-1.0.1j from OpenSSL.org and extract it. I then configured it with:

./Configure --prefix=/usr/openssl/openssl-1.0.1j darwin64-x86_64-cc zlib threads shared

With those, I was able to build, test and install without problem. That's pretty close to what you did; I simply have noted the presence of zlib (compression) and requested thread and shared library support — and specified a slightly out-of-the-way location to install it. (The top-level directory specified with --prefix existed but was empty.) I tried adding sctp to the configuration options, but no dice — an SCTP header is missing, so I didn't bother to try further.

---

Related Topics