diff --git a/doc/build-msw.md b/doc/build-msw.md index 9e4eaee3f..50b93f0f4 100644 --- a/doc/build-msw.md +++ b/doc/build-msw.md @@ -72,12 +72,12 @@ MSYS shell: mkdir miniupnpc cp *.h miniupnpc/ -Bitcoin +Dash ------- MSYS shell: - cd \bitcoin + cd \dash sh autogen.sh sh configure mingw32-make - strip bitcoind.exe + strip dashd.exe diff --git a/doc/build-osx.md b/doc/build-osx.md index c79837ca0..f299eb7d7 100644 --- a/doc/build-osx.md +++ b/doc/build-osx.md @@ -99,9 +99,9 @@ Creating a release build ------------------------ You can ignore this section if you are building `dashd` for your own use. -dashd/dash-cli binaries are not included in the Bitcoin-Qt.app bundle. +dashd/dash-cli binaries are not included in the Dash-Qt.app bundle. -If you are building `dashd` or `Bitcoin-Qt` for others, your build machine should be set up +If you are building `dashd` or `Dash-Qt` for others, your build machine should be set up as follows for maximum compatibility: All dependencies should be compiled with these flags: @@ -110,7 +110,7 @@ All dependencies should be compiled with these flags: -arch x86_64 -isysroot $(xcode-select --print-path)/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.6.sdk -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 Dash-Qt.app bundle is packaged and signed to create the .dmg disk image that is distributed. Running diff --git a/doc/build-unix.md b/doc/build-unix.md index f119aed8c..71392dfee 100644 --- a/doc/build-unix.md +++ b/doc/build-unix.md @@ -1,6 +1,6 @@ UNIX BUILD NOTES ==================== -Some notes on how to build Bitcoin in Unix. +Some notes on how to build Dash in Unix. To Build --------------------- @@ -9,7 +9,7 @@ To Build ./configure make -This will build bitcoin-qt as well if the dependencies are met. +This will build dash-qt as well if the dependencies are met. Dependencies --------------------- @@ -44,7 +44,7 @@ System requirements -------------------- C++ compilers are memory-hungry. It is recommended to have at least 1 GB of -memory available when compiling Bitcoin Core. With 512MB of memory or less +memory available when compiling Dash Core. With 512MB of memory or less compilation will take much longer due to swap thrashing. Dependency Build Instructions: Ubuntu & Debian @@ -91,7 +91,7 @@ Optional: Dependencies for the GUI: Ubuntu & Debian ----------------------------------------- -If you want to build Bitcoin-Qt, make sure that the required packages for Qt development +If you want to build Dash-Qt, make sure that the required packages for Qt development are installed. Either Qt 4 or Qt 5 are necessary to build the GUI. If both Qt 4 and Qt 5 are installed, Qt 4 will be used. Pass `--with-gui=qt5` to configure to choose Qt5. To build without GUI pass `--without-gui`. @@ -108,12 +108,12 @@ libqrencode (optional) can be installed with: sudo apt-get install libqrencode-dev -Once these are installed, they will be found by configure and a bitcoin-qt executable will be +Once these are installed, they will be found by configure and a dash-qt executable will be built by default. Notes ----- -The release is built with GCC and then "strip bitcoind" to strip the debug +The release is built with GCC and then "strip dashd" to strip the debug symbols, which reduces the executable size by about 90%. @@ -131,10 +131,10 @@ Berkeley DB It is recommended to use Berkeley DB 4.8. If you have to build it yourself: ```bash -BITCOIN_ROOT=$(pwd) +DASH_ROOT=$(pwd) -# Pick some path to install BDB to, here we create a directory within the bitcoin directory -BDB_PREFIX="${BITCOIN_ROOT}/db4" +# Pick some path to install BDB to, here we create a directory within the dash directory +BDB_PREFIX="${DASH_ROOT}/db4" mkdir -p $BDB_PREFIX # Fetch the source and verify that it is not tampered with @@ -149,8 +149,8 @@ cd db-4.8.30.NC/build_unix/ ../dist/configure --enable-cxx --disable-shared --with-pic --prefix=$BDB_PREFIX make install -# Configure Bitcoin Core to use our own-built instance of BDB -cd $BITCOIN_ROOT +# Configure Dash Core to use our own-built instance of BDB +cd $DASH_ROOT ./configure (other args...) LDFLAGS="-L${BDB_PREFIX}/lib/" CPPFLAGS="-I${BDB_PREFIX}/include/" ``` @@ -167,7 +167,7 @@ If you need to build Boost yourself: Security -------- -To help make your bitcoin installation more secure by making certain attacks impossible to +To help make your Dash installation more secure by making certain attacks impossible to exploit even if a vulnerability is found, binaries are hardened by default. This can be disabled with: @@ -191,7 +191,7 @@ Hardening enables the following features: To test that you have built PIE executable, install scanelf, part of paxutils, and use: - scanelf -e ./bitcoin + scanelf -e ./dashd The output should contain: TYPE @@ -199,13 +199,13 @@ Hardening enables the following features: * Non-executable Stack If the stack is executable then trivial stack based buffer overflow exploits are possible if - vulnerable buffers are found. By default, bitcoin should be built with a non-executable stack + vulnerable buffers are found. By default, dash should be built with a non-executable stack but if one of the libraries it uses asks for an executable stack or someone makes a mistake and uses a compiler extension which requires an executable stack, it will silently build an executable without the non-executable stack protection. To verify that the stack is non-executable after compiling use: - `scanelf -e ./bitcoin` + `scanelf -e ./dashd` the output should contain: STK/REL/PTL @@ -215,7 +215,7 @@ Hardening enables the following features: Disable-wallet mode -------------------- -When the intention is to run only a P2P node without a wallet, bitcoin may be compiled in +When the intention is to run only a P2P node without a wallet, dash may be compiled in disable-wallet mode with: ./configure --disable-wallet