On Sat, Nov 20, 2021 at 06:14:30AM +1100, Grahame Grieve wrote:
> And the rule for that is that all code your application uses must be
> signed either by you or by apple. I can include both openSSL dylibs in
> my .app package, and sign all that, but the way libssl loads libcrypto
> seems to not meet those rules - which specifically exclude symlinking
> and which specifically prohibit loading libcrypto without specifying a
> specific version.
Which means you need to build libssl in such a way that it depends
explicitly on the corresponding versioned build of libcrypto. That is
you'll need to tweak the Darwin Configuration template to specify some
additional linker options or other relevant settings.
This is not an Apple Developer community, you're perhaps better off
asking on an Apple forum, this is not an OpenSSL issue.
You have
* Application X ->
* Needs Library Y ->
* Needs Library Z
you need to know how to build Library Y so that it is compatible with
Apple's packaging requirements.
Perhaps someone has done that for MacOS, but they might not be reading
this list...
--
Viktor.
