2014-06-24 17:24:54 +01:00
|
|
|
Building libmraa {#building}
|
2014-05-29 14:51:38 +01:00
|
|
|
===============
|
|
|
|
|
|
2014-06-24 17:24:54 +01:00
|
|
|
libmraa uses cmake in order to make compilation relatively painless. Cmake runs
|
2015-01-16 14:01:43 +00:00
|
|
|
build out of tree so the recommended way is to clone from git and make a build/
|
|
|
|
|
directory.
|
2014-05-29 14:51:38 +01:00
|
|
|
|
2015-01-16 14:01:43 +00:00
|
|
|
## Build dependencies
|
|
|
|
|
Not all these are required but if you're unsure of what you're doing this is
|
|
|
|
|
what you'll need:
|
|
|
|
|
* swig 3.0.4+
|
|
|
|
|
* git
|
|
|
|
|
* python 2.7 or 3.4+ (you'll need not just the interpreter but python-dev)
|
|
|
|
|
* nodejs 0.10.x (you'll need not just the interneter but nodejs-dev)
|
|
|
|
|
* cmake 2.8.8+
|
2015-01-14 15:56:07 +00:00
|
|
|
|
2015-01-16 14:01:43 +00:00
|
|
|
## Basic build steps
|
2014-07-03 09:40:09 +01:00
|
|
|
|
2014-05-29 14:51:38 +01:00
|
|
|
~~~~~~~~~~~~~{.sh}
|
|
|
|
|
mkdir build
|
|
|
|
|
cd build
|
|
|
|
|
cmake ..
|
|
|
|
|
make
|
|
|
|
|
~~~~~~~~~~~~~
|
|
|
|
|
|
2015-01-16 14:01:43 +00:00
|
|
|
If this goes wrong and you have all the dependencies installed, then please
|
|
|
|
|
file an issue with the full output of `cmake ..` and `make` or however far you
|
|
|
|
|
got.
|
|
|
|
|
|
|
|
|
|
## Configuration flags
|
|
|
|
|
|
2015-01-14 15:56:07 +00:00
|
|
|
Our cmake configure has a number of options, cmake-gui or ccmake (cmake -i is
|
|
|
|
|
no longer with us :() can show you all the options. A few of the more common
|
|
|
|
|
ones are listed below - note that when the option starts with CMAKE_ it's an
|
|
|
|
|
option that is made available by cmake and will be similar in all cmake
|
|
|
|
|
projects. You need to add them after `cmake` but before `..`.
|
2014-05-29 14:51:38 +01:00
|
|
|
|
2015-01-14 15:56:07 +00:00
|
|
|
A few recommended options:
|
2014-05-29 14:51:38 +01:00
|
|
|
Changing install path from /usr/local to /usr
|
2014-11-09 12:26:09 +00:00
|
|
|
-DCMAKE_INSTALL_PREFIX:PATH=/usr
|
2014-05-29 14:51:38 +01:00
|
|
|
|
2015-01-14 15:56:07 +00:00
|
|
|
Building debug build - adds -g and disables optimisations - this will force a full rebuild:
|
2014-11-09 12:26:09 +00:00
|
|
|
-DCMAKE_BUILD_TYPE=DEBUG
|
2014-05-29 14:51:38 +01:00
|
|
|
|
|
|
|
|
Using clang instead of gcc:
|
2015-01-17 10:22:36 +00:00
|
|
|
-DCMAKE_C_COMPILER=/usr/bin/clang -DCMAKE_CXX_COMPILER=/usr/bin/clang++
|
2014-05-29 14:51:38 +01:00
|
|
|
|
2015-01-14 15:56:07 +00:00
|
|
|
Building with an older version of swig (swig < 3.0.2) requires the disabling of javascript:
|
2014-07-03 09:40:09 +01:00
|
|
|
-DBUILDSWIGNODE=OFF
|
2014-10-03 19:00:45 +01:00
|
|
|
|
2014-11-09 12:26:09 +00:00
|
|
|
Disabling python module building
|
|
|
|
|
-DBUILDSWIGPYTHON=OFF
|
|
|
|
|
|
|
|
|
|
Building doc, this will require sphinx & doxygen
|
|
|
|
|
-BUILDDOC=ON
|
|
|
|
|
|
2015-01-16 14:01:43 +00:00
|
|
|
## Dependancies continued
|
|
|
|
|
|
|
|
|
|
You'll need at least swig version 3.0.2 and we recommend 3.0.4 to build the
|
|
|
|
|
javascript & python modules. If your version of SWIG is older than this then
|
|
|
|
|
please see below for disabling SWIGNODE otherwise you will get a weird build
|
|
|
|
|
failure when building the js module. The python module builds with swig 2.x.
|
|
|
|
|
|
|
|
|
|
The basic build steps are as follow, we'll assume you're building from git,
|
|
|
|
|
note that if you compile with git installed your version of mraa will be tagged
|
|
|
|
|
-dirty. This simply means git wasn't installed or that you where building form
|
|
|
|
|
a tarball. You can modify build/src/version.c before running make if this is
|
|
|
|
|
incorrect. The instructions listed here all assume that build/ is an empty dir
|
|
|
|
|
that lives inside the cloned repository of mraa.
|
|
|
|
|
|
|
|
|
|
If you have multiple versions of python then mraa can get confused, we
|
|
|
|
|
recommend using virtualenv to select which version of python you want. We test
|
|
|
|
|
2.7 the most but swig will generate valid 3.x python code but we do not
|
|
|
|
|
generally support building both at once.
|
|
|
|
|
|
|
|
|
|
## Using a yocto/oe toolchain
|
2014-11-10 20:48:27 +00:00
|
|
|
|
|
|
|
|
In order to compile with a yocto/oe toolchain use the following toolchain file.
|
|
|
|
|
This works well on the edison 1.6 SDK. First source the environment file, then
|
|
|
|
|
use our cmake toolchain file.
|
|
|
|
|
|
|
|
|
|
~~~~~~~~~~~~~{.sh}
|
|
|
|
|
source /opt/poky-edison/1.6/environment-setup-core2-32-poky-linux
|
|
|
|
|
mkdir build
|
|
|
|
|
cmake -DCMAKE_TOOLCHAIN_FILE=../cmake/Toolchains/oe-sdk_cross.cmake ..
|
|
|
|
|
make
|
|
|
|
|
~~~~~~~~~~~~~
|
|
|
|
|
|
2015-01-16 14:01:43 +00:00
|
|
|
## Using coverity
|
2014-10-03 19:00:45 +01:00
|
|
|
|
|
|
|
|
Static analysis is routinely performed using coverity on libmraa's codebase.
|
|
|
|
|
This is the procedure to submit a build to coverity. You'll need to install
|
|
|
|
|
coverity-submit for your OS.
|
|
|
|
|
|
|
|
|
|
~~~~~~~~~~~~~{.sh}
|
|
|
|
|
mkdir covbuild/ && cd covbuild
|
|
|
|
|
cmake -DBUILDDOC=OFF -DBUILDSWIG=OFF ..
|
|
|
|
|
cov-build --dir cov-int make
|
2014-11-25 13:26:17 +00:00
|
|
|
tar caf mraa.tar.bz2 cov-int
|
2014-10-03 19:00:45 +01:00
|
|
|
~~~~~~~~~~~~~
|