2013-06-16 12:29:23 +02:00
Mac OS X Build Instructions and Notes
2012-12-12 17:52:38 +01:00
====================================
2013-06-16 12:29:23 +02:00
This guide will show you how to build bitcoind(headless client) for OSX.
2012-12-12 17:52:38 +01:00
Notes
-----
2014-02-26 03:35:48 +01:00
* Tested on OS X 10.6 through 10.9 on 64-bit Intel processors only.
Older OSX releases or 32-bit processors are no longer supported.
2013-06-16 12:29:23 +02:00
* All of the commands should be executed in a Terminal application. The
2012-12-12 17:52:38 +01:00
built-in one is located in `/Applications/Utilities` .
Preparation
-----------
You need to install XCode with all the options checked so that the compiler
and everything is available in /usr not just /Developer. XCode should be
available on your OS X installation media, but if not, you can get the
current version from https://developer.apple.com/xcode/. If you install
Xcode 4.3 or later, you'll need to install its command line tools. This can
be done in `Xcode > Preferences > Downloads > Components` and generally must
be re-done or updated every time Xcode is updated.
There's an assumption that you already have `git` installed, as well. If
2013-05-22 06:34:18 +02:00
not, it's the path of least resistance to install [Github for Mac ](https://mac.github.com/ )
2012-12-12 17:52:38 +01:00
(OS X 10.7+) or
[Git for OS X ](https://code.google.com/p/git-osx-installer/ ). It is also
available via Homebrew or MacPorts.
2014-01-19 13:43:15 +01:00
You will also need to install [Homebrew ](http://brew.sh )
2013-05-22 06:34:18 +02:00
or [MacPorts ](https://www.macports.org/ ) in order to install library
2012-12-12 17:52:38 +01:00
dependencies. It's largely a religious decision which to choose, but, as of
December 2012, MacPorts is a little easier because you can just install the
dependencies immediately - no other work required. If you're unsure, read
the instructions through first in order to assess what you want to do.
Homebrew is a little more popular among those newer to OS X.
The installation of the actual dependencies is covered in the Instructions
sections below.
Instructions: MacPorts
----------------------
### Install dependencies
Installing the dependencies using MacPorts is very straightforward.
2014-01-16 06:42:21 +01:00
sudo port install boost db48@+no_java openssl miniupnpc autoconf pkgconfig automake
2012-12-12 17:52:38 +01:00
2014-02-26 03:35:48 +01:00
Optional: install Qt4
sudo port install qt4-mac qrencode protobuf-cpp
2012-12-12 17:52:38 +01:00
### Building `bitcoind`
1. Clone the github tree to get the source code and go into the directory.
git clone git@github.com:bitcoin/bitcoin.git bitcoin
cd bitcoin
2014-02-26 03:35:48 +01:00
2. Build bitcoind (and Bitcoin-Qt, if configured):
2012-12-12 17:52:38 +01:00
2013-11-11 04:11:33 +01:00
./autogen.sh
./configure
make
2012-12-12 17:52:38 +01:00
3. It is a good idea to build and run the unit tests, too:
2013-12-11 23:11:21 +01:00
make check
2012-12-12 17:52:38 +01:00
2014-01-19 13:43:15 +01:00
Instructions: Homebrew
2012-12-12 17:52:38 +01:00
----------------------
#### Install dependencies using Homebrew
2014-02-03 15:55:18 +01:00
brew install autoconf automake berkeley-db4 boost miniupnpc openssl pkg-config protobuf qt
2012-12-12 17:52:38 +01:00
2014-01-19 13:43:15 +01:00
Note: After you have installed the dependencies, you should check that the Homebrew installed version of OpenSSL is the one available for compilation. You can check this by typing
2013-04-22 10:26:42 +02:00
openssl version
2014-01-19 13:43:15 +01:00
into Terminal. You should see OpenSSL 1.0.1f 6 Jan 2014.
2013-04-22 10:26:42 +02:00
2014-01-19 13:43:15 +01:00
If not, you can ensure that the Homebrew OpenSSL is correctly linked by running
2013-04-22 10:26:42 +02:00
brew link openssl --force
Rerunning "openssl version" should now return the correct version.
2012-12-12 17:52:38 +01:00
### Building `bitcoind`
1. Clone the github tree to get the source code and go into the directory.
2013-12-11 04:58:06 +01:00
git clone https://github.com/bitcoin/bitcoin.git
2012-12-12 17:52:38 +01:00
cd bitcoin
2013-11-11 04:11:33 +01:00
2. Build bitcoind:
2012-12-12 17:52:38 +01:00
2013-11-11 04:11:33 +01:00
./autogen.sh
./configure
make
2012-12-12 17:52:38 +01:00
2013-11-11 04:11:33 +01:00
3. It is a good idea to build and run the unit tests, too:
2012-12-12 17:52:38 +01:00
2013-12-11 23:11:21 +01:00
make check
2012-12-12 17:52:38 +01:00
Creating a release build
------------------------
2014-02-26 03:35:48 +01:00
You can ignore this section if you are building `bitcoind` for your own use.
2012-12-12 17:52:38 +01:00
2014-02-26 03:35:48 +01:00
bitcoind/bitcoin-cli binaries are not included in the Bitcoin-Qt.app bundle.
2012-12-12 17:52:38 +01:00
2014-02-26 03:35:48 +01:00
If you are building `bitcoind` or `Bitcoin-Qt` for others, your build machine should be set up
2012-12-12 17:52:38 +01:00
as follows for maximum compatibility:
All dependencies should be compiled with these flags:
2014-02-26 03:35:48 +01:00
-mmacosx-version-min=10.6
-arch x86_64
-isysroot $(xcode-select --print-path)/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.6.sdk
2012-12-12 17:52:38 +01:00
For MacPorts, that means editing your macports.conf and setting
`macosx_deployment_target` and `build_arch` :
2014-02-26 03:35:48 +01:00
macosx_deployment_target=10.6
build_arch=x86_64
2012-12-12 17:52:38 +01:00
... and then uninstalling and re-installing, or simply rebuilding, all ports.
As of December 2012, the `boost` port does not obey `macosx_deployment_target` .
Download `http://gavinandresen-bitcoin.s3.amazonaws.com/boost_macports_fix.zip`
2014-02-26 03:35:48 +01:00
for a fix.
2012-12-12 17:52:38 +01:00
2014-02-26 03:35:48 +01:00
Once dependencies are compiled, see release-process.md for how the Bitcoin-Qt.app
bundle is packaged and signed to create the .dmg disk image that is distributed.
2012-12-12 17:52:38 +01:00
Running
-------
It's now available at `./bitcoind` , provided that you are still in the `src`
directory. We have to first create the RPC configuration file, though.
Run `./bitcoind` to get the filename where it should be put, or just try these
commands:
echo -e "rpcuser=bitcoinrpc\nrpcpassword=$(xxd -l 16 -p /dev/urandom)" > "/Users/${USER}/Library/Application Support/Bitcoin/bitcoin.conf"
chmod 600 "/Users/${USER}/Library/Application Support/Bitcoin/bitcoin.conf"
When next you run it, it will start downloading the blockchain, but it won't
2014-02-26 03:35:48 +01:00
output anything while it's doing this. This process may take several hours;
you can monitor its process by looking at the debug.log file, like this:
tail -f $HOME/Library/Application\ Support/Bitcoin/debug.log
2012-12-12 17:52:38 +01:00
Other commands:
./bitcoind -daemon # to start the bitcoin daemon.
2014-02-26 03:35:48 +01:00
./bitcoin-cli --help # for a list of command-line options.
./bitcoin-cli help # When the daemon is running, to get a list of RPC commands