3
### Checking dependencies
5
Check all the dependencies needed for the project to be built:
9
(this will return the list of dependencies). Install the returned dependencies:
11
$ apt-get install <list_of_dependencies>
16
You can check the needed packages by using:
18
$ dpkg-checkdependencies
21
and install the list of needed dependencies returned. Once done, execute:
23
$ mkdir build && cd build
24
$ cmake -DCMAKE_INSTALL_PREFIX=/usr ../..
27
where <n> is the number of cores available to use for building.
28
You can use ccache also if expected to build several times (apt-get install ccache)
33
Once built, into build folder, execute:
37
where <n> is the number of cores available to use for executing the tests in parallel
40
### Building the package
42
NOTE: Before building the package it is needed run a hook which updates debian folder. You have to execute
43
that hook from project folder:
45
$ ./debian/bileto_pre_release_hook
48
If all goes well, no response should be returned.
50
You can build the deb package in current arch by executing:
53
$ dpkg-buildpackage -b
56
in case you want to skip signage and dependencies to build a test package, you can use some additional params:
58
$ dpkg-buildpackage -nc -us -uc -d -b
61
besides, if you are in a lxd container and want to build a package for that container architecture:
63
$ dpkg-buildpackage -nc -us -uc -d -b --target-arch <arch> -a <arch> -j<n>
66
where <arch> is the architecture of the environment and <n> the number of cores to use
68
Depending on the release the soname of the resultant library will be on or another. You can query file:
70
tools/get_soversion.sh
73
the soversion that will be used for the library. The resultant .deb package will be like:
75
libmessaging-framework<apiversion>-<soversion>_XXX_<arch>.deb