commit | 0bc363e6b3760abc2c9a500b6de1f4d32889d9e7 | [log] [tgz] |
---|---|---|
author | David Wagner <david.wagner@intel.com> | Tue Mar 17 16:47:26 2015 +0100 |
committer | Eric Laurent <elaurent@google.com> | Fri Apr 24 13:39:11 2015 -0700 |
tree | 7d7b75dd996f06cbd27d17ab6c3f13d524639ba0 | |
parent | 0fe8b7d6edc1b27c71c8317d2b816534db7a8637 [diff] |
travis: run 'ldconfig' after 'sudo make install' In 327b1a48e2fe539c0ca5414ce9c98b2405536a09 we changed the installation prefix to /usr because we witnessed errors during unit tests using the python bindings. We initially thought that /usr/local/lib wasn't in the loader's default paths but it turns out it is. In fact, it only is the loader's cache that was outdated and needed to be regenerated. That's what ldconfig does. 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
.