On May 15, 2010, at 10:00 PM, Patrick Rutkowski wrote:
> I should mention that the obvious suggestion of "You need to link your
> framework against OpenSSL" is not what I'm looking for.
Well, are you specifying -lssl and -lcrypto in other linker flags? If not, you
must.
> If I link my framewor
I should mention that the obvious suggestion of "You need to link your
framework against OpenSSL" is not what I'm looking for.
If I link my framework statically against OpenSSL, then I force the clients of
my framework to use that static version of OpenSSL, which I don't want.
If I link my fram
I'm building a Framework which internally uses OpenSSL, and exposes a sort of
OpenSSL wrapper for various small purposes.
However, when linking the framework, Xcode complains of missing symbols like:
_ERR_error_string_n
_ERR_clear_error
_SSL_CTX_free
_SSL_CTX_new
_ERR_get_error
_SSL_library_init
