There is another Thread about Xojo users having issues with libcrypto.
It boils down to the fact that Apple wants Developers to include their own build/version of libcrypto. And/or on the newst macOS (especially arm64 | when using the newst macOS SDK, such as Xojo 2021r1 does) to link against a specific version. But since one can’t know which libcrypto version(s) Apple provides with it’s (upcoming) OSes - better include the version you need yourself.
So the big question for many of us is… How to build OpenSSL (libcrypto) and include it in a Xojo built app?
If you’re interested - here is an example project: macOS: OpenSSL - Bring your Own
This example project shows how you can build your own OpenSSL Library from Source as a Universal .dylib (arm64 and x86_64), include it in a Xojo project - and finally use it in your application. It includes
- HowTo.txt - which explains all the steps
- Build.sh - A Shell Script you can use as a template to build the current versions of the OpenSSL Library yourself
- Example Xojo Project - showing how to include your own built .dylib’s in your application
And just for fun… I have compiled the outdated OpenSSL 0.9.8zh as Universal (arm64 and x86_64). That’s a bit more tricky since you have to add/modify the Configuration for arm64 yourself. Notes are also in the example project. Not that I recommend that - but in case you are using Declares that only work with that libcrypto-version, and no longer with 1.1.1 - this might be a temporary solution to make your app working for a M1 Mac (as an arm64 build) without fiddling with existing Declares.