This is a summary of the documentation in the Bitcoin Core repository. Don't hesitate to read it for more information.

All steps are to be run from your terminal emulator, i.e. the command line.

1. Ensure the dependencies are installed. The following lists include some optional dependencies. Don't hesitate to consult the links below, adapt the dependencies to your needs, and let me know if any are out of date here. Note that ccache isn't strictly required, but you'll probably want to install it (see below). You'll also need a compiler like GCC and/or Clang installed. Refer to doc/dependencies.md for more information.
   • Linux (see doc/build-unix.md for details): sudo apt-get install automake autotools-dev bsdmainutils build-essential ccache clang gcc git libboost-dev libboost-filesystem-dev libboost-system-dev libboost-test-dev libevent-dev libminiupnpc-dev libnatpmp-dev libqt5gui5 libqt5core5a libqt5dbus5 libsqlite3-dev libtool libzmq3-dev pkg-config python3 qttools5-dev qttools5-dev-tools qtwayland5 systemtap-sdt-dev
   • macOS (with command line tools and Homebrew already installed, see doc/build-osx.md for details): brew install automake boost ccache git libevent libnatpmp libtool llvm miniupnpc pkg-config python qrencode qt@5 sqlite zeromq
2. Download the Bitcoin source files by git cloning the repository.
   • git clone https://github.com/bitcoin/bitcoin.git
3. Berkeley DB (BDB) is only needed for legacy wallet compatibility or testing, i.e. before the current descriptor wallets that use SQLite3. Note that you can disable legacy wallet support by passing --without-bdb to your ./configure options below.
   • To install BDB 4.8, a backward-compatible legacy version, run brew install berkeley-db@4 for macOS, and for Linux see the Bitcoin Core build-*.md documentation for your operating system (the legacy install_db4.sh script was removed in Bitcoin Core v25 with PR 26834).
   • If you have another version of BDB already installed that you wish to use, simply add --with-incompatible-bdb to your ./configure flags below instead. This option is recommended unless you specifically need BDB 4.8.
4. Compile from a tagged release branch, unless you wish to test a specific branch or PR.
   • git tag -n | sort -V to see tags and descriptions ordered by most recent last
   • git checkout <TAG> to use a tagged release, for example: git checkout v0.21.0
   • If you want to pull down a PR or specific branch from the remote repository to build and test locally, here is how.
5. Compile Bitcoin from source.
   • ./autogen.sh
   • ./configure --with-incompatible-bdb --enable-suppress-external-warnings

     or, if you are using BDB 4.8
     

       export BDB_PREFIX='<PATH-TO>/db4'
       ./configure BDB_LIBS="-L${BDB_PREFIX}/lib -ldb_cxx-4.8" BDB_CFLAGS="-I${BDB_PREFIX}/include" --enable-suppress-external-warnings

   • You can omit the --enable-suppress-external-warnings flag if you want to see compiler warnings related to external libraries used by Bitcoin Core
   • make, or if you have multiple CPU cores, which is the usual case nowadays, you can tell make to use all of them and reduce compile time significantly with
   • make -j "$(($(nproc) + 1))" on Linux, or
   • make -j "$(($(sysctl -n hw.physicalcpu) + 1))" on macOS
6. Pro tips.

   You can run ./configure --help to see all the various configuration options. It's a long list, so it may be more practical to search for what you want with grep: ./configure --help | grep -A1 "your-search-term". The three options I use the most often are --enable-suppress-external-warnings and --with-incompatible-bdb as mentioned above, and --enable-debug for debug builds for reviewing and testing pull requests.

   If you're re-compiling frequently (e.g. for testing small changes), as long as you're not changing the build configuration you can skip directly to the make -j <n> step for subsequent builds.

   On the other hand, when you change the build configuration (e.g. for a fuzz build), or you are building a branch containing substantial changes to the autoconf/automake scripts, or when the build isn't working, it's often best to start with a clean slate using make clean or make distclean. Here's a complete example:

   ./autogen.sh && ./configure <flags> && make clean && make -j <n>

   To compile with Clang instead of GCC (e.g. for fuzzing, sanitizers, better warnings/errors, or to use less resources), add CC=clang CXX=clang++ to your configure flags:

   ./configure CC=clang CXX=clang++

   To compile for fuzz testing, build with Clang using the following:
   

     ./autogen.sh
     ./configure --enable-fuzz --with-sanitizers=address,fuzzer,undefined CC=clang CXX=clang++
     make clean
     make -j <n>

   The steps for fuzz builds with macOS are different (see this link for more details):
   

     ./autogen.sh
     ./configure --enable-fuzz --with-sanitizers=address,fuzzer,undefined CC=$(brew --prefix llvm)/bin/clang CXX=$(brew --prefix llvm)/bin/clang++ --disable-asm --enable-suppress-external-warnings
     make clean
     make -j <n>

   You can test running a single fuzzer with, for example: FUZZ=process_message ./src/test/fuzz/fuzz

   To compile with sanitizers (credit to Marco Falke for this section), build with Clang using the following:

   • MSan: Compiling with MSan is quite involved. For running tests with MSan, it's probably easiest to just compile normally and then invoke valgrind ./src/test/test_bitcoin or ./test/functional/test_runner.py --valgrind instead. Alternatively, you can use the ./ci/ system to run any sanitizer task.
   • Other sanitizers: Simply append --with-sanitizers=undefined,integer CC=clang CXX=clang++ to your ./configure call (or --with-sanitizers=address, ...). Then, run the tests normally, using the env vars as needed:
     

       export LSAN_OPTIONS="suppressions=$(pwd)/test/sanitizer_suppressions/lsan"
       export TSAN_OPTIONS="suppressions=$(pwd)/test/sanitizer_suppressions/tsan:halt_on_error=1:second_deadlock_stack=1"
       export UBSAN_OPTIONS="suppressions=$(pwd)/test/sanitizer_suppressions/ubsan:print_stacktrace=1:halt_on_error=1:report_error_type=1"

   See the Sanitizers section of the Bitcoin Core developer notes for more information.

   Be sure to use ccache to speed up your builds. You can also gain time by building only what you need. See the Bitcoin Core productivity notes for more.

   If you build often, bash aliases may be helpful for abstracting the repetitive details down to short commands. These are probably not a great example, but here are mine.

7. Troubleshooting.

   If you're seeing any odd issues while compiling, try using make clean or make distclean and rebuild from scratch as described above.

   If that doesn't work, or if you are seeing linker issues, the header and compilation might be out of sync and you may want to ensure that you are building from a clean tree. If you are using ccache, try clearing the cache by running ccache -C (see ccache -h for help) and then rebuilding.

   If that doesn't solve it, you can also run git clean -f -x -d and rebuild. This wipes everything in the tree that doesn't belong to git, so be careful that you don't have anything else in the directory that you don't want to lose and move it out first.

8. Run the unit tests.
   • make check, or
   • make -j "$(($(nproc)+1))" check to use multithreading on Linux, or
   • make -j "$(($(sysctl -n hw.physicalcpu)+1))" check to use multithreading on macOS
   • See the Bitcoin Core unit tests documentation for more info.
9. Run the functional tests. From the repository root:
   • test/functional/test_runner.py to run the standard test suite (try test/functional/test_runner.py -j 60 or a similar high number to run the tests more quickly in parallel)
   • test/functional/.py to run an individual test file
   • test/functional/test_runner.py --extended to run the extended test suite
   • test/functional/test_runner.py --help to see the various options for running tests
   • See the Bitcoin Core functional tests documentation for more info.

Cheers,

Jon Atack