I installed the new "threading" version of Armory under Mac OS X Mountain Lion. Although still slightly experimental, it is the version that etotheipi says is going to be the official version real soon now, when Armory goes into beta (from alpha, see https://bitcointalk.org/index.php?topic=56424.msg1315445#msg1315445
I use homebrew to install the dependencies. On a Mac, there are at least three competing package managers for Unix/Linux software, homebrew, macports and fink. I would be seriously surprised if it matters which one you choose, so don't let this thread decide for you. Also, I have chosen to use the system's Python installation, and *not* install homebrews own python. This is more in line with homebrew's philosophy of not duplicating packages, and is one of the reasons I chose homebrew. But again, I really cannot claim superiority of this approach [in fact, I really don't know what I am doing
], and I am sure both choices are equally good for Armory.
So here are the steps (partly from memory, forgive me if I forgot something essential!). All of this is done in a Terminal window.
0) Be sure to have the newest xcode installed, including the command line tools.
1) Install homebrew by copy-pasting the ruby installation command from the homebrew web page into the Terminal, see http://mxcl.github.com/homebrew/
1a) You probably want to run brew doctor
and fix any fixable problems before proceeding.
2) Install the first batch of prerequisites for Armory
brew install cryptopp
brew install swig
brew install sip
brew install qt
brew install pyqt
brew install berkeley-db
You have now installed Python stuff in /usr/local/lib. The standard OS X Python will not find them, unless you add the directory to PYTHONPATH, e.g. by adding this line to the .profile file in your home directory
Note that the .profile file starts with a period, meaning that it is a hidden file.
3) You also need some Python packages not in homebrew. These can be installed with Python's easy_install or with pip (easy_install pip). I think pip makes it easier to uninstall later, but neither of them do a proper job when it comes to package management
WARNING: Don't uncritically copy-past the BERKELEYDB_INCDIR path above, it will
change as new versions come along. Instead, type it using TAB-completion.
4) Get the Armory source code, and switch to the threading branch (this assumes you want it placed as a subdirectory under your home directory, replace the first cd command if you want it elsewhere).
git clone git://github.com/etotheipi/BitcoinArmory.git
git checkout threading
(I am no git wizard - this could undoubtedly be done as one git command.)
5) Compile the C++/swig part of Armory.
export CFLAGS=”-arch x86_64″
export ARCHFLAGS=”-arch x86_64″
6) Return to the main Armory directory
7) Try it out!
Make sure you have internet, that the Satoshi client is running and (preferably) that it has finished catching up.
8 ) Have fun. Although I do have a bitcoin address in my signature, I really think you should donate to the Armory guys instead!