On 14 Jan 2014, at 09:42, Charles Srstka <cocoa...@charlessoft.com> wrote:
> On Jan 14, 2014, at 3:19 AM, jonat...@mugginsoft.com wrote: > >> The only problem with retaining it is the extra complexity involved in >> integrating the static library build into the project and upgrading the >> source. > > One trick that can help is that OpenSSL is in MacPorts, so you can just set > up a symlink to the static library in /opt/local/lib, and then just run > /opt/local/port selfupdate and /opt/local/port upgrade outdated every once in > a while (or you can just set up a LaunchDaemon to run those commands > periodically). This will keep your copy of OpenSSL and libcrypto up to date, > at least. > Took a while to get around to confirming this but I did use the MacPorts approach - it was simply easier than building libcrypto from source within my project (https://github.com/sqlcipher/openssl-xcode). It should be noted that lib crypto.a has a dependency on libz.a. -lz is therefore required in other linker flags. Jonathan _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
