| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Bug 246391
Change-Id: I662b7b0f90c97cb169978e1b64ad1fe32c440cf5
Signed-off-by: Jean-Michel Trivi <jmtrivi@google.com>
|
| |
|
|
|
|
|
|
|
|
| |
Ctest related files and definitions were at the
source root although we try to keep it simple.
Move all ctest related files and definition in
a ctest directory.
Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
|
| |
|
|
|
|
|
|
|
| |
The root CMakeList was including every test directories
directly, although it should be kept simple.
Move the inclusions to a dedicated CMakeList in test.
Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds functionnal test to the PFW.
The execution of these tests needs the test-subsystem to be compiled.
The tests can be launch with 'make test'.
We set the environment vars in the cmake.
Then we launch ACTCampaignEngine.py.
Temporary files like build time conf files are placed on the build directory.
Next steps :
- Test-subsystem needs to be reworked (with binding python).
Signed-off-by: Adrien M <adrienx.martin@intel.com>
|
| |
|
|
|
|
|
| |
Possibility to run the test without having to lunch the 'make install'
command.
Signed-off-by: Adrien M <adrienx.martin@intel.com>
|
| |
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
When working with the parameter-framework,
the remote-process command is very handy.
Nevertheless it has long commands and it is easy to make mistakes.
Add a bash completion script to complete:
- hostnames
- frequently used port
- commands and arguments based on the remote usage (help command)
Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These bindings for the parameter-framework generic connector use "SWIG" to
generate:
- a C++ file providing a basic bridge between C++ and Python (must be compiled
to a shared library named "_PyPfw.so" - the name is important)
- a Python module wrapping it inside a Proxy class, re-creating the same
classes as the parameter-framework generic connector.
See http://www.swig.org for the full SWIG documentation.
They are generated and compiled on-the-fly as part of the build process.
Change-Id: If7c67f1178dcc9f438cf037246eb77bbd74b689a
Signed-off-by: David Wagner <david.wagner@intel.com>
Signed-off-by: Sebastien Gonzalve<sebastien.gonzalve@intel.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
Cmake can manage test with ctest. Running them when make test
is run. Unfortunately the only automatic tests the pfw has
(fix point parameter test) are not declared in cmake.
Add a test target and declare the fix point parameter test in cmake.
Thus a simple make test after the make install will run all tests.
Signed-off-by: Kevin Rocard <kevinx.rocard@intel.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
BZ: 207083
License headers were missing in CMake makefiles.
This patch adds the 3-clause BSD license header to each CMakeLists.txt.
Change-Id: Ia4da92e139e02d6348d655d0d88a16166d8431ca
Signed-off-by: Mattijs Korpershoek <mattijsx.korpershoek@intel.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This tool can be used to validate a set of xml files against w3c
schemas.
It scans a directory recursively and checks for .xml files in it.
For each file, it extracts the current schema file based on a convention
(the corresponding schema file must have the same name as the root node)
which is used in the parameter-framework.
Change-Id: I27e32028e39a450ed18f86cb095348f73d59ade5
|
| |
|
|
|
|
|
|
|
| |
When performing the tutorials, I wanted to use the
tools/xmlGenerator/hostDomainGenerator.sh script.
In order to do that, i had to copy manually my scripts files
to the pfwInstalledDir/bin directory.
This patchs completes the install target by copying the needed files
|
| |
|
|
| |
Signed-off-by: David Wagner <david.wagner@intel.com>
|
|
|
1) Generate the Makefiles with "cmake";
2) compile all targets with "make".
Signed-off-by: David Wagner <david.wagner@intel.com>
|
