configure -help to see the various options: $. The most important of these is the configure script that offers a number of different options to customize the build process. The autogen.sh script creates a set of automatic configuration scripts that will interrogate your system to discover the correct settings and ensure you have all the necessary libraries to compile the code. Src/Makefile.am: installing `src/build-aux/depcomp'
autogen.shĬonfigure.ac:12: installing `src/build-aux/config.guess'Ĭonfigure.ac:12: installing `src/build-aux/config.sub'Ĭonfigure.ac:37: installing `src/build-aux/install-sh'Ĭonfigure.ac:37: installing `src/build-aux/missing'
BITCOIN CORE UBUNTU CODE
The autogen/configure/make introduced in 0.9 is likely to be the build system used for all future versions of the code and is the system demonstrated in the following examples. Follow the instructions for the version you want to compile. Older versions use a simple Makefile and work slightly differently from the following example. The Bitcoin Core build process was changed to use the autogen/configure/make system starting with version 0.9. Assuming the prerequisites are installed, you start the build process by generating a set of build scripts using the autogen.sh script.
BITCOIN CORE UBUNTU INSTALL
If this happens because you missed a prerequisite, you can install it and then resume the build process from where you left off. If these prerequisites are missing, the build process will fail with an error. These are libraries that must be present on your system before you can begin to compile bitcoin.
BITCOIN CORE UBUNTU FOR MAC OS X
Alternative instructions for Mac OS X and Windows can be found in the doc directory, as build-osx.md or build-msw.md, respectively.Ĭarefully review the build prerequisites, which are in the first part of the build documentation. Review the instructions for compiling the bitcoind command-line client on your platform by typing more doc/build-unix.md. In this chapter, we will build the command-line bitcoin client, also known as bitcoind on Linux. Review the main documentation located in README.md in the bitcoin directory by typing more README.md at the prompt and using the space bar to progress to the next page. The source code includes documentation, which can be found in a number of files. To synchronize the local code with this version, use the git checkout command: $ git checkout v0.9.0rc1 From the preceding list, select the highest version release, which at this writing was v0.9.0rc1. Stable releases that can be run on production systems have no suffix. By convention, release candidates, which are intended for testing, have the suffix “rc”.
The list of tags shows all the released versions of bitcoin.
First, to find the available tags, we use the git tag command: $ git tag Tags are used by the developers to mark specific releases of the code by version number. This will synchronize the local copy with a specific snapshot of the code repository identified by a keyword tag. Before compiling the code, select a specific version by checking out a release tag. Change to this directory by typing cd bitcoin at the prompt: $ cd bitcoinīy default, the local copy will be synchronized with the most recent code, which might be an unstable or beta version of bitcoin. When the git cloning operation has completed, you will have a complete local copy of the source code repository in the directory bitcoin. Follow the documentation that comes with the code even if it differs from the instructions you see here, and don’t be surprised if the output displayed on your screen is slightly different from the examples here. The instructions and resulting output might vary from version to version.
0 kommentar(er)
