85
edits
Changes
Jump to navigation
Jump to search
Line 28:
Line 28: + + − +
protobuf-devel
CRIU uses the [https://github.com/protobuf-c/protobuf-c C language bindings] of [https://developers.google.com/protocol-buffers/ Google Protocol Buffers] for serialization. The <code>protoc</code> tool is required at build time and <code>libprotobuf-c.so</code> is required at build time and at run time, assuming dynamic linking.
CRIU uses the [https://github.com/protobuf-c/protobuf-c C language bindings] of [https://developers.google.com/protocol-buffers/ Google Protocol Buffers] for serialization. The <code>protoc</code> tool is required at build time and <code>libprotobuf-c.so</code> is required at build time and at run time, assuming dynamic linking.
[[CRIT]] also uses python language bindings of Google Protocol Buffers and requires descriptor.proto from developer files that could be found in protobuf-devel package.
==== Distribution Packages ====
==== Distribution Packages ====
The easiest approach for most would be to install distribution packages. RPM package names: <code>protobuf-c-compiler</code>, <code>protobuf-c-devel</code>. Debian package names: <code>protobuf-c-compiler</code>, <code>libprotobuf-c0-dev</code>.
The easiest approach for most would be to install distribution packages. RPM package names: <code>protobuf-c-compiler</code>, <code>protobuf-c-devel</code>, <code>protobuf-devel</code>, <code>protobuf-python</code>. Debian package names: <code>protobuf-c-compiler</code>, <code>libprotobuf-c0-dev</code>, <code>protobuf-compiler</code>, <code>protobuf-python</code>.
==== Building Protocol Buffers From Source ====
==== Building Protocol Buffers From Source ====