Building Armory From Source
The latest stable version of Armory is available in precompiled, GPG-signed binaries for Windows, Ubuntu/Debian, and Mac. You can download them from the Releases page. Non-Debian-based Linux users will have to compile from source.
Compiling in Linux has proven to be quite easy. There are only a couple dependencies, and they’re all versionless, so there are no games you have to play with system library versions in order to get it to work.
If you want to compile in Windows, the build process is far from simple, but extremely well-documented. Do it at your own risk! It involves downloading and manually installing about 7 packages, then using Microsoft Visual Studio to compile the C++ code and create a python-module. But it does work!
Verifying Source Code Authenticity
The latest stable version or Armory is always be tagged in the git repository by its version number, and signed with the Armory signing key (4922589A). For releases 0.93.3 and earlier, the old Armory signing key (98832223) was used.
Here’s how you download the Armory signing key directly into your keyring from the Ubuntu keyserver, and then verify the signature using
git tag -v:
$ gpg --recv-keys --keyserver keyserver.ubuntu.com 4922589A gpg: requesting key 4922589A from hkp server keyserver.ubuntu.com gpg: key 4922589A: public key "goatpig (Offline signing key for Armory releases) <email@example.com>" imported $ git tag -v v0.96 object a3d01aa72293f82c3ef3f1d29f93c83ad70099f4 type commit tag v0.96 tagger goatpig <firstname.lastname@example.org> 1493581585 +0200 v0.96 gpg: Signature made Sun 30 Apr 2017 03:46:25 PM EDT using RSA key ID 4922589A gpg: Good signature from "goatpig (Offline signing key for Armory releases) <email@example.com>"
The above example is specifically for checking the tag for version “v0.96”, which may not be the latest version by the time you are reading these instructions. You can replace it with the latest version number posted on our website. All releases can be viewed on the github releases page. All major releases are accompanied by a signed tag.
To checkout and build a specific version, simply use
git checkout [tag] before the
make command in the Ubuntu build instructions below. For instance, to build version 0.96, you would simply use:
$ $ git checkout v0.96 Note: checking out 'v0.96'. ... HEAD is now at a3d01aa... bump version
Ubuntu Build Instructions
In Ubuntu, open a terminal (Applications → Accessories → Terminal) and copy in each of the following lines one at a time (omit the dollar sign at the beginning of each line):
$ sudo apt-get install git-core build-essential pyqt4-dev-tools swig libqtcore4 libqt4-dev python-qt4 python-dev python-twisted python-psutil automake autotools-dev libtool $ git clone git://github.com/goatpig/BitcoinArmory.git $ cd BitcoinArmory $ git submodule init $ git submodule update $ ./autogen.sh $ ./configure $ make $ python ArmoryQt.py
Alternatively you can run “sudo make install” after building and it and it will install Armory onto your Ubuntu system, including but shortcuts in your the Applications –> Internet menu.
NOTE: The above instructions do not check Armory’s signatures the as shown in the previous section. If you know the latest version (0.96 as of this writing), then you can add the verification checks before the “make” command, as seen below:
$ sudo apt-get install git-core build-essential pyqt4-dev-tools swig libqtcore4 libqt4-dev python-qt4 python-dev python-twisted python-psutil $ git clone git://github.com/goatpig/BitcoinArmory.git $ cd BitcoinArmory $ git checkout v0.96 # put latest version number here $ git tag -v v0.96 # confirm signatures before continuing $ git submodule init $ git submodule update $ ./autogen.sh $ ./configure $ make $ python ArmoryQt.py
Mac OS X Build Instructions
To build Armory on Mac OS X, you can follow the directions found in the “osxbuild” directory in the Armory github project. Specifically:
The instructions are plain-text and can be viewed directly from the Github webpage.
Windows Build Instructions
Please note that it is a very involved process to build from source on Windows! We have done our best to make this as straightforward as possible, but it may still require some patience and possibly some experience with MS Visual Studio.
These instructions are also in plaintext and can be viewed directly from the Github webpage.