Topic: Armory on macOS: Requires openssl installed with homebrew (Read 171 times)
While I think you can compile your way around OpenSSL on Qt if you don't mind a lot of pain, I don't think you can on Python. IIRC, even on the latest Python (3.8), you must have OpenSSL for things like Python's PRNGs, even if you roll your own version of Python. There's been vague talk of making this more modular one day so that people can drop in other libraries. I'll expect that one when Hell freezes over.
The issue is more PyQt than Mac tbh. Some modules depend on OpenSSL (QtNetwork is the chief culprit), and PyQt includes everything Qt has to offer by default. Using Qt at the C++ level, you could probably avoid that kind of overzealous linkage.
ugh.
Imustnotusethisiopportunitytoexpressrevulsionatmacosplatform Imustnotusethisiopportunitytoexpressrevulsionatmacosplatform Imustnotusethisiopportunitytoexpressrevulsionatmacosplatform Imustnotusethisiopportunitytoexpressrevulsionatmacosplatform Imustnotusethisiopportunitytoexpressrevulsionatmacosplatform Imustnotusethisiopportunitytoexpressrevulsionatmacosplatform
so what depends on openssl? libbtc?
Just an announcement in case anybody else has the same problem:
I just installed Armory on a relatively new Mac (running OS X Mojave, not the brand new Catalina). Armory did not work, it could not open the app. Starting the relevant script inside the Armory.app folder showed that the error was that a library in /usr/local/opt/openssl/lib could not be opened, that folder was missing.
Installing openssl with Homebrew (see https://brew.sh) fixed it!
It seems to be an error in building the MacOS executable, where OpenSSL has not been bundled as it should have been.
I just installed Armory on a relatively new Mac (running OS X Mojave, not the brand new Catalina). Armory did not work, it could not open the app. Starting the relevant script inside the Armory.app folder showed that the error was that a library in /usr/local/opt/openssl/lib could not be opened, that folder was missing.
Installing openssl with Homebrew (see https://brew.sh) fixed it!
It seems to be an error in building the MacOS executable, where OpenSSL has not been bundled as it should have been.
Jump to: