| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
In 327b1a48e2fe539c0ca5414ce9c98b2405536a09 we changed the installation prefix
to /usr because we witnessed errors during unit tests using the python
bindings.
We initially thought that /usr/local/lib wasn't in the loader's default paths
but it turns out it is. In fact, it only is the loader's cache that was
outdated and needed to be regenerated. That's what ldconfig does.
Signed-off-by: David Wagner <david.wagner@intel.com>
|
| |
|
|
|
|
|
|
|
| |
The pfw can not currently be used from c code.
Add an c api. It does not target a perfect one/one mapping with the c++ one,
but rather aim ease of use and type safety (as far as possible in c).
Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
CMake defaults to /usr/local which results in libraries being installed in
/usr/local/lib. Unfortunately, this path isn't in the loader's default
locations.
The canonical installation path is /usr. /usr/local is recommended for stuff
not handled by the package manager but in the context of the CI, this isn't
relevant.
Signed-off-by: David Wagner <david.wagner@intel.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The parameter framework can build lots of components including but not
limited to core c++ lib, c api, python api, bash completion...
All those modules are not always wanted, especially if they have
external dependencies as it force the builder to install them.
Conditionally define non core build modules.
The builder can disable feature by providing -D <FEATURE>=OFF
to deactivate them.
The following options are available:
- PYTHON_BINDINGS: Break swig dependencies
- BASH_COMPLETION: If the target does not have bash
- COVERAGE: Default to off, set to on to build c/c++ with coverage flags.
Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Test were enabled with the enable_testing command.
Nevertheless this method is very basic.
Include CTest, as this cmake utility enables automatic
build + test + coverage generation + memchek test (valgrind) + sending report
in one command: ```make Experimental```
There are far more features added by this utility, see:
http://www.cmake.org/Wiki/CMake/Testing_With_CTest#Dashboards
Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
|
| |
|
|
|
|
|
|
| |
Do not execute tests if the build fails.
Indent the commands for readability.
Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
|
| |
|
|
|
|
|
|
| |
ctest by default put all logs in a file and never display it even if a test fails.
Add the relevant option to output on failure.
Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The c pfw interface (following patch) needs a recent gcc to compile.
Gcc and gcov version need to be align, thus gcov is updated too.
Ctest analyse the gcov output, as a result it must be align with
it (gcov 2.7 changed it's report format).
Ctest, and cmake are packaged together.
Conclusion: update cmake and gcc packages.
Unfortunatly ubuntu backport does not provide a recent enough
version, that is why ppa were used instead.
Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
|
| |
|
|
|
|
|
| |
The skeleton plugin is an example and as such needs to work out-of-the-box.
Make travis build it to ensure we don't break anything.
Signed-off-by: David Wagner <david.wagner@intel.com>
|
|
|
Travis will build each new commit and each pull request and publish the results
here:
https://travis-ci.org/01org/parameter-framework
and on the #parameter-framework channel on FreeNode.
This commit also adds a build status icon in the Readme.
Signed-off-by: David Wagner <david.wagner@intel.com>
|
