Files

Marko Budiselić 958bc870b3 Migrate to toolchain-v2 (#33 )

* GCC_VERSION=10.2.0
* BINUTILS_VERSION=2.35.1
* GDB_VERSION=10.1 (except centos-7 8.3)
* CMAKE_VERSION=3.18.4
* CPPCHECK_VERSION=2.2
* LLVM_VERSION=11.0.0
* SWIG_VERSION=4.0.2

2020-11-12 20:18:11 +01:00

Migrate to toolchain-v2 (#33 )

2020-11-12 20:18:11 +01:00

toolchain

Migrate to toolchain-v2 (#33 )

2020-11-12 20:18:11 +01:00

.gitignore

Migrate to Clang 8

2019-04-19 12:34:50 +02:00

README.md

Migrate to toolchain-v2 (#33 )

2020-11-12 20:18:11 +01:00

util.sh

Migrate to toolchain-v2 (#33 )

2020-11-12 20:18:11 +01:00

README.md

Memgraph Build and Run Environments

Toolchain Installation Procedure

Download the toolchain for your operating system from one of the following links (current active toolchain is toolchain-v2):

Extract the toolchain with the following command:

tar xzvf {{toolchain-archive}}.tar.gz -C /opt

Check and install required toolchain runtime dependencies by executing (e.g., on Debian 10):

./environment/os/debian-10.sh check TOOLCHAIN_RUN_DEPS
./environment/os/debian-10.sh install TOOLCHAIN_RUN_DEPS

Activate the toolchain:

source /opt/toolchain-v2/activate

Toolchain Upgrade Procedure

Build a new toolchain for each supported OS (latest versions).
If the new toolchain doesn't compile on some supported OS, the last compilable toolchain has to be used instead. In other words, the project has to compile on the oldest active toolchain as well. Suppose some changes/improvements were added when migrating to the latest toolchain; in that case, the maintainer has to ensure that the project still compiles on previous toolchains (everything from init script to the actual code has to work on all supported operating systems).