commit | a9be2d378b7ad84e679a48efa81f42fb54f85d9a | [log] [tgz] |
---|---|---|
author | Jean-Michel Trivi <jmtrivi@google.com> | Wed Jul 15 15:37:57 2015 -0700 |
committer | Jean-Michel Trivi <jmtrivi@google.com> | Wed Jul 15 17:09:51 2015 -0700 |
tree | 587d34728dac3517a213d6d2a9a6ebdecd4e7531 | |
parent | c99720d29f2ee618cc74c9336d2cd2a26544c020 [diff] |
Drop release v2.6.0+no-stlport Bug 246391 Change-Id: I662b7b0f90c97cb169978e1b64ad1fe32c440cf5 Signed-off-by: Jean-Michel Trivi <jmtrivi@google.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
.