commit | 69c025eb4b42d203b0e6859d5c350cead91d4208 | [log] [tgz] |
---|---|---|
author | David Wagner <david.wagner@intel.com> | Tue Apr 14 18:13:11 2015 +0200 |
committer | Eric Laurent <elaurent@google.com> | Fri Apr 24 13:39:14 2015 -0700 |
tree | 4c30b1ad4a4d1338b1ecbd22172a80e01fb44a84 | |
parent | 079608996beadb477b8d11777905cc8003b7af94 [diff] |
python: prefer 2.7.x and make sure interpreter and libs are aligned CMake's find_package command makes it possible to specify a version. Take advantage of that to favor the interpreter's version to 2.7 and then pin the library's version to the very same version as the interpreter. This does not ensure that 2.7.x is used (e.g. if 2.7.x is not present, another version will be used) but it helps a lot. Signed-off-by: David Wagner <david.wagner@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
.