commit | 61e221838cf44e1dfd767d82c5d899f8a55d1330 | [log] [tgz] |
---|---|---|
author | David Wagner <david.wagner@intel.com> | Fri Oct 24 18:07:26 2014 +0200 |
committer | David Wagner <david.wagner@intel.com> | Fri Oct 24 18:07:26 2014 +0200 |
tree | 4fd80604ea1ca31f2de12b9d6bfd2a263c776bd7 | |
parent | 1e4132e01cac27e9d83052d81a406e830616193f [diff] | |
parent | 187e350b2f46a53819fe76a1eeda72036be2d512 [diff] |
Merge pull request #19 from krocard/Remove_useless_log_on_xml_generation_failure Remove flood debug trace on xml generation error
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