The standard C/C++ development headers on your system.
On GNU/Linux, the terminfo development libraries, which may beÂ part of a ncurses development package (e.g. `libncurses-dev` on Debian/Ubuntu, but `ncurses-devel` on CentOS).
A Go environment with a recent 64-bit version of the toolchain. Note that the Makefile enforces the specific version required, as it is updated frequently.
Git 1.9+, we recommend v2.20+
Bash (4+ is preferred)
GNU Make (4.2+ is known to work)
NodeJS 12.x and Yarn 1.7+
Yacc or Bison
Bazelisk (you can use Bazel directly instead of Bazelisk, although Bazelisk makes sure youâre using the same version that we use in CI)
If you're running macOS, a full installation of XCode is necessary.
Get the CockroachDB code
mkdir -p $(go env GOPATH)/src/github.com/cockroachdb
cd $(go env GOPATH)/src/github.com/cockroachdb
git clone https://github.com/cockroachdb/cockroach
Note: it is important to ensure the CockroachDB sources are positioned correctly relative to `$GOPATH`. Otherwise, the builds will fail.
Run `make build`, `make test`, or anything else our Makefile offers. Note:Â you might need to runÂ make clean first if you're seeing an error likeÂ
make: /usr/local/Cellar/cmake/3.13.4/bin/cmake: No such file or directory.
If you wish to reuse our builder image instead of installing all the dependencies manually, prefix the make command with build/builder.sh; for example build/builder.sh make build.
Note that the first time you run make, it can take some time to download and install various dependencies. After running make build, the cockroach executable will be in your current directory and can be run as shown in Starting with CockroachDB.
Note that if you use the builder image, you should ensure that your Docker installation grants 4GB or more of RAM to containers. On some systems, the default configuration limits containers to 2GB memory usage and this can be insufficient to build/link a CockroachDB executable.