@@ -22,19 +22,16 @@ Xcode 4.3 or later, you'll need to install its command line tools. This can
22
22
be done in ` Xcode > Preferences > Downloads > Components ` and generally must
23
23
be re-done or updated every time Xcode is updated.
24
24
25
- There's an assumption that you already have ` git ` installed, as well . If
25
+ There's also an assumption that you already have ` git ` installed. If
26
26
not, it's the path of least resistance to install [ Github for Mac] ( https://mac.github.com/ )
27
27
(OS X 10.7+) or
28
28
[ Git for OS X] ( https://code.google.com/p/git-osx-installer/ ) . It is also
29
29
available via Homebrew or MacPorts.
30
30
31
31
You will also need to install [ Homebrew] ( http://brew.sh )
32
32
or [ MacPorts] ( https://www.macports.org/ ) in order to install library
33
- dependencies. It's largely a religious decision which to choose, but, as of
34
- December 2012, MacPorts is a little easier because you can just install the
35
- dependencies immediately - no other work required. If you're unsure, read
36
- the instructions through first in order to assess what you want to do.
37
- Homebrew is a little more popular among those newer to OS X.
33
+ dependencies. It's largely a religious decision which to choose, however, Homebrew
34
+ is now used for building release versions.
38
35
39
36
The installation of the actual dependencies is covered in the Instructions
40
37
sections below.
@@ -44,8 +41,6 @@ Instructions: MacPorts
44
41
45
42
### Install dependencies
46
43
47
- Installing the dependencies using MacPorts is very straightforward.
48
-
49
44
sudo port install boost db48@+no_java openssl miniupnpc autoconf pkgconfig automake
50
45
51
46
Optional: install Qt4
@@ -80,7 +75,7 @@ Note: After you have installed the dependencies, you should check that the Homeb
80
75
81
76
openssl version
82
77
83
- into Terminal. You should see OpenSSL 1.0.1f 6 Jan 2014.
78
+ into Terminal. You should see OpenSSL 1.0.1h 5 Jun 2014.
84
79
85
80
If not, you can ensure that the Homebrew OpenSSL is correctly linked by running
86
81
103
98
./configure
104
99
make
105
100
106
- 3 . It is a good idea to build and run the unit tests, too :
101
+ 3 . It is also a good idea to build and run the unit tests:
107
102
108
103
make check
109
104
@@ -131,7 +126,7 @@ For MacPorts, that means editing your macports.conf and setting
131
126
... and then uninstalling and re-installing, or simply rebuilding, all ports.
132
127
133
128
As of December 2012, the ` boost ` port does not obey ` macosx_deployment_target ` .
134
- Download ` http ://gavinandresen-bitcoin.s3.amazonaws.com/boost_macports_fix.zip`
129
+ Download ` https ://gavinandresen-bitcoin.s3.amazonaws.com/boost_macports_fix.zip`
135
130
for a fix.
136
131
137
132
Once dependencies are compiled, see release-process.md for how the Bitcoin-Qt.app
@@ -149,13 +144,14 @@ commands:
149
144
echo -e "rpcuser=bitcoinrpc\nrpcpassword=$(xxd -l 16 -p /dev/urandom)" > "/Users/${USER}/Library/Application Support/Bitcoin/bitcoin.conf"
150
145
chmod 600 "/Users/${USER}/Library/Application Support/Bitcoin/bitcoin.conf"
151
146
152
- When next you run it, it will start downloading the blockchain, but it won't
147
+ The next time you run it, it will start downloading the blockchain, but it won't
153
148
output anything while it's doing this. This process may take several hours;
154
149
you can monitor its process by looking at the debug.log file, like this:
155
150
156
151
tail -f $HOME/Library/Application\ Support/Bitcoin/debug.log
157
152
158
153
Other commands:
154
+ -------
159
155
160
156
./bitcoind -daemon # to start the bitcoin daemon.
161
157
./bitcoin-cli --help # for a list of command-line options.
0 commit comments