Well, thanks to some helpful insights from Peter I now have two
solutions which I thought I'd share.
Solution 1 - use NSLookupAndBindSymbol().
This looks beyond the specific module being looked at and considers the
global address space. This means it will look for the definition in a
dynamically linked libcrypto.dylib.
Solution 2 - Statically link with a libcrypto.a (built from the openssl
source distro - though I had to run ranlib an additional time to get it
to link correctly). This forces the symbols to actually be defined in
the module being loaded and NSLookupSymbolInModule will find them.
In both cases underscores are needed everywhere :)
Sean
_______________________________________________
unix-porting mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/unix-porting
Do not post admin requests to the list. They will be ignored.
