Replies: 1 comment 5 replies
-
maybe ossl-ssl.xcframework ossl-crypto.xcframework, could you try modify https://github.com/simdsoft/1kiss/blob/dev/src/openssl/dist1.sh like https://github.com/simdsoft/1kiss/blob/dev/src/curl/dist1.sh#L7 ? |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
@halx99 The latest Axmol has changed the OpenSSL libraries, and this is causing failed Apple builds in my projects. There are 3rd party libraries that link to OpenSSL, either to "ssl" and "crypto", or to "OpenSSL::Crypto" and "OpenSSL::SSL", but they are no longer working, since those libraries no longer exist, and have been combined together into one "openssl" library in the xcframework. This "openssl" name is not the conventional naming or setup of OpenSSL, so 3rd party libraries can't detect it.
The only way to get the build working is to manually modify the cmake files in any library used in the project that depends on OpenSSL to ensure it links with "openssl", and only for Apple, and this needs to happen any time the 3rd party libs are updated.
All platforms other than Apple are fine, and use "OpenSSL::Crypto"/"OpenSSL::SSL", so this is just an issue with the setup for Apple.
Is there chance you can just set up the xcframework to have both crypto and ssl as separate libraries using standard target names in cmake, and perhaps even set aliases for them, "OpenSSL::Crypto"/"OpenSSL::SSL" if possible?
Beta Was this translation helpful? Give feedback.
All reactions