e5d2ff5d45
e351a16a2a Remove reference to deprecated RPC call in build instructions (Michael Goldstein) a6f16f1b1a Docs: Add disable-wallet section to OSX build instructions (Michael Goldstein) Pull request description: The `disable-wallet` section was mentioned in the `Berkeley DB` section of the OSX build instructions, but the section did not actually exist. This PR ports the section from the Unix build instructions. Tree-SHA512: e32f10f3b92307325f2101e89d3e18c89346916e70117c208ad7441170c4aee65b636ea4f7dd1cb0ecf0e800c1aa7c37fa73125e69ecdd539bc862e651b79b16 # Conflicts: # doc/build-unix.md
2.0 KiB
macOS Build Instructions and Notes
The commands in this guide should be executed in a Terminal application.
The built-in one is located in /Applications/Utilities/Terminal.app.
Preparation
Install the macOS command line tools:
xcode-select --install
When the popup appears, click Install.
Then install Homebrew.
Base build dependencies
brew install automake libtool pkg-config
If you want to build the disk image with make deploy (.dmg / optional), you need RSVG
brew install librsvg
Building
It's possible that your PATH environment variable contains some problematic strings, run
export PATH=$(echo "$PATH" | sed -e '/\\/!s/ /\\ /g') # fix whitespaces
Next, follow the instructions in build-generic
Disable-wallet mode
When the intention is to run only a P2P node without a wallet, Bitcoin Core may be compiled in disable-wallet mode with:
./configure --disable-wallet
In this case there is no dependency on Berkeley DB 4.8.
Mining is also possible in disable-wallet mode using the getblocktemplate RPC call.
Running
Dash Core is now available at ./src/dashd
Before running, it's recommended that you create an RPC configuration file.
echo -e "rpcuser=dashrpc\nrpcpassword=$(xxd -l 16 -p /dev/urandom)" > "/Users/${USER}/Library/Application Support/DashCore/dash.conf"
chmod 600 "/Users/${USER}/Library/Application Support/DashCore/dash.conf"
The first time you run dashd, it will start downloading the blockchain. This process could take several hours.
You can monitor the download process by looking at the debug.log file:
tail -f $HOME/Library/Application\ Support/DashCore/debug.log
Other commands:
./src/dashd -daemon # Starts the dash daemon.
./src/dash-cli --help # Outputs a list of command-line options.
./src/dash-cli help # Outputs a list of RPC commands when the daemon is running.