sikkienl/dash
1
0
Fork 0
mirror of https://github.com/dashpay/dash.git synced 2024-12-26 04:22:55 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #4435

Browse Source 
92ddf2c Update OS X build instructions (Michael Ford)
This commit is contained in:
Wladimir J. van der Laan 2014-06-28 14:59:54 +02:00
commit 55b27206d0
No known key found for this signature in database
GPG Key ID: 74810B012346C9A6
1 changed files with 8 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/build-osx.md
View File

@ -22,7 +22,7 @@ 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 done in `Xcode > Preferences > Downloads > Components` and generally must
be re-done or updated every time Xcode is updated. be re-done or updated every time Xcode is updated.
There's an assumption that you already have `git` installed, as well. If There's also an assumption that you already have `git` installed. If
not, it's the path of least resistance to install [Github for Mac](https://mac.github.com/) not, it's the path of least resistance to install [Github for Mac](https://mac.github.com/)
(OS X 10.7+) or (OS X 10.7+) or
[Git for OS X](https://code.google.com/p/git-osx-installer/). It is also [Git for OS X](https://code.google.com/p/git-osx-installer/). It is also
@ -30,11 +30,8 @@ available via Homebrew or MacPorts.
You will also need to install [Homebrew](http://brew.sh) You will also need to install [Homebrew](http://brew.sh)
or [MacPorts](https://www.macports.org/) in order to install library or [MacPorts](https://www.macports.org/) in order to install library
dependencies. It's largely a religious decision which to choose, but, as of dependencies. It's largely a religious decision which to choose, however, Homebrew
December 2012, MacPorts is a little easier because you can just install the is now used for building release versions.
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 The installation of the actual dependencies is covered in the Instructions
sections below. sections below.
@ -44,8 +41,6 @@ Instructions: MacPorts
### Install dependencies ### Install dependencies
Installing the dependencies using MacPorts is very straightforward.
sudo port install boost db48@+no_java openssl miniupnpc autoconf pkgconfig automake sudo port install boost db48@+no_java openssl miniupnpc autoconf pkgconfig automake
Optional: install Qt4 Optional: install Qt4
@ -80,7 +75,7 @@ Note: After you have installed the dependencies, you should check that the Homeb
openssl version openssl version
into Terminal. You should see OpenSSL 1.0.1f 6 Jan 2014. into Terminal. You should see OpenSSL 1.0.1h 5 Jun 2014.
If not, you can ensure that the Homebrew OpenSSL is correctly linked by running If not, you can ensure that the Homebrew OpenSSL is correctly linked by running
@ -103,7 +98,7 @@ PATH.
./configure ./configure
make make
3. It is a good idea to build and run the unit tests, too: 3. It is also a good idea to build and run the unit tests:
make check make check
@ -131,7 +126,7 @@ For MacPorts, that means editing your macports.conf and setting
... and then uninstalling and re-installing, or simply rebuilding, all ports. ... and then uninstalling and re-installing, or simply rebuilding, all ports.
As of December 2012, the `boost` port does not obey `macosx_deployment_target`. As of December 2012, the `boost` port does not obey `macosx_deployment_target`.
Download `http://gavinandresen-bitcoin.s3.amazonaws.com/boost_macports_fix.zip` Download `https://gavinandresen-bitcoin.s3.amazonaws.com/boost_macports_fix.zip`
for a fix. for a fix.
Once dependencies are compiled, see release-process.md for how the Bitcoin-Qt.app Once dependencies are compiled, see release-process.md for how the Bitcoin-Qt.app
@ -149,13 +144,14 @@ commands:
echo -e "rpcuser=bitcoinrpc\nrpcpassword=$(xxd -l 16 -p /dev/urandom)" > "/Users/${USER}/Library/Application Support/Bitcoin/bitcoin.conf" 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" 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 The next time you run it, it will start downloading the blockchain, but it won't
output anything while it's doing this. This process may take several hours; 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: you can monitor its process by looking at the debug.log file, like this:
tail -f $HOME/Library/Application\ Support/Bitcoin/debug.log tail -f $HOME/Library/Application\ Support/Bitcoin/debug.log
Other commands: Other commands:
-------
./bitcoind -daemon # to start the bitcoin daemon. ./bitcoind -daemon # to start the bitcoin daemon.
./bitcoin-cli --help # for a list of command-line options. ./bitcoin-cli --help # for a list of command-line options.