Thanks for the MR. I do not have a Mac to test this, though, so I'd prefer to get some feedback from other MacOS users if this fixes some of the outstanding issues on MacOS.

Also, I noticed that you hard-coded "libcrypto.46.dylib" and "libssl.46.dylib" - is this a good idea / is this always the file name on all versions of MacOS and unlikely to change in the future? Or can this be made to dynamically find the proper file name?

I thought the 'lib*.46.dylib' was just a last resort as a default to return, but it turns out that is what is needed for loading libadobe on MacOS with Homebrew openssl libs.

MacOS doesn't actually have the files in its directory, but they are in its 'dyld shared cache' to be loaded. If you try to load something more generic like /usr/lib/libcrypto.dylib the OS will crash your entire program with an error saying "don't do that, the API is not stable". Explicitly using the Apple Security Framework as I had before does not work because libadobe looks for 'OpenSSL version' which is not available.

So this code tries the .46 version (available since 2020) and then the .35 version (available since 2015) and tests loading libadobe for each; if neither works it gives up with a message seen if running in the terminal.

There's also:

• code to get the environment variables on a Mac if running from a terminal instead of the GUI
• avoids checking if the path exists when loading libraries specified in env variables on Mac, as the files are probably not there

How do we find someone else with a Mac to review this? Add to the Mobilread thread?