Changes

CRIU is mostly written in C and the build system is based on Makefiles. Thus just install standard <code>gcc</code> and <code>make</code> setspackages (on Debian, <code>[https://packages.debian.org/build-essential build-essential]</code> will pull in both at once).

Some additional steps If you are required if you're using Debian. * For native compilation on Debian based systems, install the <code>build-essential</code> package.* On a modern Debian based x86_64 you will need to install the <code>lib32stdc++6</code> and <code>lib32z1</code> packages. For cross compiling for ARM and AArch64, the Linaro use distribution packages or download prebuilt toolchains are a good choice which are ia32 architecture binariesfrom Linaro.

CRIU uses the [https://developers.google.com/protocol-buffers/ Google Protocol Buffers] to read and write [[images]] and thus requires [https://github.com/protobuf-c/protobuf-c C language bindings]. The <code>protoc</code> tool is required at build time and the <code>libprotobuf-c.so</code> shared object is required at build and run time. [[CRIT]] also uses python language bindings for protocol buffers and requires the <code>descriptor.proto</code> file from devel set that can be typically found in the <code>provided by a distribution's protobuf-devel</code> development package.

** <code>protobuf-pythonc-devel</code>

** <code>protobuf-c-develpython</code>

If you would like to build from source, you can use the following commands to obtain the source code repositories, configure, and build the code. On a Debian based system, you may have to do install <code>autoconf curl g++ libtool</code> packages first.