commit | 19aa05b33990302d2388b8c90eeb71a3509e6320 | [log] [tgz] |
---|---|---|
author | Jules Clero <julesx.clero@intel.com> | Wed Feb 11 09:42:20 2015 +0100 |
committer | Eric Laurent <elaurent@google.com> | Fri Apr 24 13:39:12 2015 -0700 |
tree | bae705f20690f4b697f8bf355d9b6bd2e22ee346 | |
parent | d770f7a4082873887833d886fb8aeacf1eeb57af [diff] |
Fix tUINT32_ARRAY index overflow test This test was using the wrong array size. It leads to false positive. Signed-off-by: Jules Clero <julesx.clero@intel.com>
The parameter-framework is a plugin-based and rule-based framework for handling parameters. This means that you can:
The parameter-framework can be used to set the value of alsa controls (switches, volumes, etc.) on smartphones/tablets based on parameter-framework rules (in this example, they transcribe use-cases). For accessing parameters (i.e. alsa controls), you may use the alsa plugin.
The filesystem plugin can be used to write parameters in files. This is particularly useful for files in /sys
managing GPIOs.
The parameter-framework's core comes in the form of a shared library. Its client has to provide:
At runtime, the most usual communication between the client and the parameter-framework are:
The parameter-framework comes with several tools, including a command-line interface: remote-process
.
See the wiki on github.
Run cmake .
then make
. You may then install libraries, headers and binaries with make install
. By default, they are installed under /usr/local
on unix OSes; if you want to install them under a custom directory, you may do so by passing it to the cmake .
command; e.g.
cmake -DCMAKE_INSTALL_PREFIX=/path/to/custom/install .
Also, CMake can build a project out-of-tree, which is the recommended method:
mkdir /path/to/build/directory cd /path/to/build/directory cmake /path/to/parameter-framework/sources make
After an install you may want to run the parameter-framework tests with make test
.