commit | d9526499d6ab53b7d13d1434f748f6f2161c2e0a | [log] [tgz] |
---|---|---|
author | Sebastien Gonzalve <oznog@zarb.org> | Thu Feb 20 22:28:03 2014 +0100 |
committer | David Wagner <david.wagner@intel.com> | Thu Sep 11 14:25:02 2014 +0200 |
tree | 8d2e2db275800821d4bf8873fc16b686bca60b2d | |
parent | ffbf43b383bb8693741430b02c24dbc9b127f7f7 [diff] |
Remove using std::XXX from headers This is a bad practice to have using in headers because it pollutes the namespace of any user of that header.
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