commit | 7364dba71a9cd1c6cfd11945df67654ddc08582d | [log] [tgz] |
---|---|---|
author | Andreas Gampe <agampe@google.com> | Wed Oct 07 17:50:09 2015 +0000 |
committer | Andreas Gampe <agampe@google.com> | Wed Oct 07 17:50:09 2015 +0000 |
tree | 743e40a10091c5134e19eb6e3ee4b100acdd6fec | |
parent | 175805bbb161cdd271e4f851de69eaf08f846399 [diff] |
Revert "Temporarily disable due to python-related build issues" This reverts commit 175805bbb161cdd271e4f851de69eaf08f846399. Seems the merger was blocked, all the underlying changes are now in. Change-Id: I92802dde26f868caa757247c055ec40557606798
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
.