The CMake build system can build the entire codebase, including proton-c, and all its language bindings.
The following prerequisites are required to do a full build on RPM-based systems (RHEL, Fedora, etc.). If you do not wish to build a given language binding you can omit the devel package for that language.
# Required dependencies $ yum install gcc gcc-c++ make cmake libuuid-devel # Dependencies needed for SSL support $ yum install openssl-devel # Dependencies needed for Cyrus SASL support $ yum install cyrus-sasl-devel cyrus-sasl-plain cyrus-sasl-md5 # Dependencies needed for bindings $ yum install swig # Required for all bindings $ yum install python-devel # Python $ yum install ruby-devel rubygem-minitest # Ruby $ yum install jsoncpp-devel # C++ optional config file # Dependencies needed to generate documentation $ yum install python-sphinx # Python $ yum install rubygem-yard # Ruby $ yum install doxygen # C, C++
The following prerequisites are required to do a full build on Debian-based systems (Ubuntu). If you do not wish to build a given language binding you can omit the dev package for that language.
# Required dependencies $ apt-get install gcc g++ cmake cmake-curses-gui uuid-dev # Dependencies needed for SSL support $ apt-get install libssl-dev # dependencies needed for Cyrus SASL support $ apt-get install libsasl2-2 libsasl2-dev libsasl2-modules # dependencies needed for bindings $ apt-get install swig python-dev ruby-dev # dependencies needed for python docs $ apt-get install python-sphinx
From the directory where you found this
$ mkdir build $ cd build # Set the install prefix. You may need to adjust it depending on your # system. $ cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DSYSINSTALL_BINDINGS=ON # Omit the docs target if you do not wish to build or install # documentation. $ make all docs # Note that this step will require root privileges. $ make install
When make install completes, all installed files are listed in the
install_manifest.txt file. The contents of this file may be used to uninstall.
This describes how to build the Proton library on Windows using Microsoft Visual C++.
The Proton build uses the CMake tool to generate the Visual Studio project files. These project files can then be loaded into Visual Studio and used to build the Proton library.
The following packages must be installed:
Additional packages are required for the language bindings:
To generate the Visual Studio project files, from the directory where you found this
> mkdir build > cd build > cmake ..
If CMake doesn't guess things correctly, useful additional arguments are:
-G "Visual Studio 10" -DSWIG_EXECUTABLE=C:\swigwin-2.0.7\swig.exe
Refer to the CMake documentation for more information.
Build and install from a command prompt (using msbuild):
> cmake --build . --target install --config RelWithDebInfo
ALL_BUILD project into Visual Studio:
ALL_BUILDproject file or Proton solution file - it should be in the
builddirectory you created above.
Note that if you wish to build debug version of Proton for use with Swig bindings on Windows, you must have the appropriate debug target libraries to link against.
Proton can use the http://libuv.org IO library on any platform where it is available. Install the libuv library and header files and adapt the instructions for building on Linux.
The libuv library is not required on Linux or Windows, but if you wish you can use it instead of the default native IO by running cmake with
Most dynamic languages provide a way for asking where to install libraries in order to place them in a default search path.
SYSINSTALL_BINDINGS is enabled (
CMAKE_INSTALL_PREFIX does not affect the location for where the language bindings (Python and Ruby) are installed. For those elements, the location is determined by the language interpreter itself; that is, each interpreter is queried for the proper location for extensions.
SYSINSTALL_BINDINGS is disabled (
OFF), Proton installs all dynamic language bindings into a central, default location:
In order to use these bindings, you'll need to configure your interpreter to load the bindings from the appropriate directory.
You can configure the build to install a specific binding to the location specified by the system interpreter with the SYSINSTALL_[LANGUAGE] options, where [LANGUAGE] is one of PYTHON or RUBY.
$ cmake .. -DSYSINSTALL_PYTHON=ON
To disable any given language bindings, you can use the BUILD_[LANGUAGE] option where [LANGUAGE] is one of PYTHON or RUBY or GO, for example:
$ cmake .. -DBUILD_PYTHON=OFF