macOS alternative setup instructions¶
Important note about Gatekeeper¶
Starting with macOS 10.15 Catalina, applications launched from the macOS Terminal application (or any other terminal emulator) are subject to the same system security policies that are applied to applications launched from the Dock. This means that if you download executable binaries using a web browser, macOS will not let you execute those from the Terminal by default. In order to get around this issue you can take two different approaches:
xattr -r -d com.apple.quarantine /path/to/folderwhere
path/to/folderis the path to the enclosing folder where the executables you want to run are located.
Open “System Preferences” -> “Security and Privacy” -> “Privacy” and then scroll down to “Developer Tools”. Then unlock the lock to be able to make changes and check the checkbox corresponding to your terminal emulator of choice. This will apply to any executable being launched from such terminal program.
Note that this section does not apply to executables installed with
Homebrew, since those are automatically un-quarantined by
brew itself. This
is however relevant for most 3rd Party Toolchains.
Additional notes for MacPorts users¶
While MacPorts is not officially supported in this guide, it is possible to use
MacPorts instead of Homebrew to get all the required dependencies on macOS.
Note also that you may need to install
cargo for the Python
dependencies to install correctly.