summaryrefslogtreecommitdiffstats
path: root/bindings
Commit message (Collapse)AuthorAgeFilesLines
* change to system python and swigreplicant-6.0-alpha-0004replicant-6.0-alpha-0003replicant-6.0-alpha-0002replicant-6.0-alpha-0001Wolfgang Wiedmeyer2016-01-141-22/+12
| | | | | Change-Id: Iefb42d20372dc90f4673277905dc6be52e5c1db1 Signed-off-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
* Drop release v2.6.0+no-stlportJean-Michel Trivi2015-07-155-14/+37
| | | | | | | Bug 246391 Change-Id: I662b7b0f90c97cb169978e1b64ad1fe32c440cf5 Signed-off-by: Jean-Michel Trivi <jmtrivi@google.com>
* Fix mac build: do not hardcode linux pathsJean-Michel Trivi2015-04-281-2/+2
| | | | Change-Id: I70996fcbc0c0d60c51fde207dfd8cae25265c79b
* python bindings: activate thread-safety code generationDavid Wagner2015-04-241-1/+1
| | | | | | | | | | | | | | | | | The Parameter Framework may spawn a thread listening to request for command execution. In this case, whenever a command produces a log, a callback function provided by the client is called. When the client is a python script using the python bindings, this causes a python function to be called in a different context than the main thread. This can only work safely if a specific lock is held before hand; see https://docs.python.org/2/c-api/init.html#non-python-created-threads Fortunately, SWIG can generate the corresponding code automatically using %module(threads=1, ...) mymodule Signed-off-by: David Wagner <david.wagner@intel.com>
* python: prefer 2.7.x and make sure interpreter and libs are alignedDavid Wagner2015-04-241-2/+5
| | | | | | | | | | | 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>
* Dissociate 'make test' & 'make install'Adrien M2015-04-242-2/+15
| | | | | | | Possibility to run the test without having to lunch the 'make install' command. Signed-off-by: Adrien M <adrienx.martin@intel.com>
* Install c parameter-framework bindingsKevin Rocard2015-04-241-0/+2
| | | | | | | | C bindings were compiled and tested but never installed. Add the missing install command. Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
* python bindings: install modules to the dist-packages directoryDavid Wagner2015-04-241-2/+14
| | | | | | | | Use python to get the OS's directory name for dist-packages. The python bindings (low-level shared library and python proxy class) are then installed to that path, prefixed by the cmake install prefix. Signed-off-by: David Wagner <david.wagner@intel.com>
* cmake/python bindings: reorganize include_directories() instructionsDavid Wagner2015-04-241-4/+2
| | | | | | | | | | 1) PYTHON_INCLUDE_PATH is deprecated in favor of PYTHON_INCLUDE_DIRS 2) adding the current source directory to the include dirs is useless since it is implicit. 3) group all include_directories() instructions to the same place in the makefile. Signed-off-by: David Wagner <david.wagner@intel.com>
* cmake/python bindings: remove duplicated PythonLibs inclusionDavid Wagner2015-04-241-6/+1
| | | | | | | | It was included by both find_package() and include(); the success of the inclusion was then checked manually. Instead, find_pacakge(PythonLibs REQUIRED) does the inclusion and the checking automatically. Signed-off-by: David Wagner <david.wagner@intel.com>
* C pfw bindingsKevin Rocard2015-04-245-0/+1141
| | | | | | | | | The pfw can not currently be used from c code. Add an c api. It does not target a perfect one/one mapping with the c++ one, but rather aim ease of use and type safety (as far as possible in c). Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
* Modularise build using cmake optionsKevin Rocard2015-04-241-1/+4
| | | | | | | | | | | | | | | | | The parameter framework can build lots of components including but not limited to core c++ lib, c api, python api, bash completion... All those modules are not always wanted, especially if they have external dependencies as it force the builder to install them. Conditionally define non core build modules. The builder can disable feature by providing -D <FEATURE>=OFF to deactivate them. The following options are available: - PYTHON_BINDINGS: Break swig dependencies - BASH_COMPLETION: If the target does not have bash - COVERAGE: Default to off, set to on to build c/c++ with coverage flags. Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
* android/python bindings: force gcc and 32bits compilationDavid Wagner2015-04-231-0/+5
| | | | | | | | | | | Since Android only provides a 32bits version of the python interpreter and libs, we need to compile for 32bits even on 64bits hosts. Also, since it seems that clang is the default compiler for host, we need to explicitely forbid it as long as the parameter-framework is compiled with gcc. Change-Id: I5d484c0e58c304680192f443acd81258de179e52 Signed-off-by: David Wagner <david.wagner@intel.com>
* Merge pull request #49 from pafonso/iminleg_rebaseDavid Wagner2015-02-182-4/+1
|\ | | | | Iminleg rebase
| * Create output host library directory if neededPhilippe Afonso2015-02-181-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | The directory where to generate output may not exists leading generation to failure. This patch adds the directory creation and thus makes sure generation won't fail for this reason. Change-Id: I1cee75d6d7921315dc3a928245499bde447c3639 Tracked-On: https://jira01.devtools.intel.com/browse/IMINAN-19676 Signed-off-by: Sebastien Gonzalve <sebastien.gonzalve@intel.com>
| * Adding XML format to Criteria export tuning I/FPatrick Benavoli2015-02-181-4/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | BZ: 209937 The "listCriteria" command returns the list of criteria in a human readable way. However, external tools that require to know this list of criteria have trouble parsing this output. An XML output would solve the issue. Changed "listCriteria" command to accept "XML" as first and only argument. In the end, listCriteria command accepts the 3 following forms: - listCriteria => will list the criteria states and type content in a human readable format - listCriteria csv|CSV => will list the criteria states and type content in a CSV format - listCriteria xml|XML => will list the criteria states and type content in an XML format Removed python binding accordingly. Change-Id: Ib060ec0a5d1ff87ba6c25caf4e0d5839a7927715 Signed-off-by: Patrick Benavoli <patrick.benavoli@intel.com> Signed-off-by: Sebastien Gonzalve <sebastien.gonzalve@intel.com>
* | Low case cmake command in bindings for consistencyKevin Rocard2015-02-161-10/+10
| | | | | | | | | | | | | | | | | | Some cmake commands were in big case in the python binding cmake. As all others are in low case, put everything in low case. Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
* | Remove CXX compiler verbose flag for swig bindingKevin Rocard2015-02-161-1/+1
| | | | | | | | | | | | | | | | | | | | When compiling swig generated files, the CXX compiler flag list included -v. This leaded to unnecessary log output during compilation. Remove the flag Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
* | Fix cmake set_property in python bindingsKevin Rocard2015-02-161-2/+2
|/ | | | | | | | | | | | | `SET_SOURCE_FILES_PROPERTIES(pfw.i PROPERTIES SWIG_FLAGS "-v" "-Wall" "-Werror")` sets 2 variables: - `SWIG_FLAGS="-v"` - `-Wall="-Werror"` which is obviously not what was wanted. Replace by `SET_PROPERTY(SOURCE pfw.i PROPERTY SWIG_FLAGS "-v" "-Wall" "-Werror")` that only sets `SWIG_FLAGS="-v -Wall -Werror"`. Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
* python bindings: add a READMEDavid Wagner2015-01-281-0/+29
| | | | | Change-Id: I361ef7ca42fb79f61164f227b8f7893f90332b62 Signed-off-by: David Wagner <david.wagner@intel.com>
* ParameterMgr: add a method to forcefully disable the remote interfaceDavid Wagner2015-01-281-0/+3
| | | | | | | | | | | | | | | In some setup, users might not want to start the remote interface even if the toplevel configuration file allows it. The parameter-framework client can now override the remote interface starting policy. This was, until now, only dictated by the 'TuningAllowed' attribute in the toplevel configuration file and the presence of the libremote-processor library. This method is forwarded to the connectors and the bindings. Change-Id: Ib6dc272dfc7114125fdafd1a58642cde88847752 Signed-off-by: David Wagner <david.wagner@intel.com>
* bindings: bind ILogger and setLogger()David Wagner2015-01-284-5/+68
| | | | | | | | | | | | | | | This will allow users of the parameter-framework bindings to set a logger; without it, the parameter-framework wasn't able to log anything. Some SWIG features and workarounds must be activated in order to: - Support nested classes; - Derive bound classes and allow C++ to call back the user-created objects; - Properly handle exceptions that may be raised upon errors happening on the user side. Change-Id: I955152a4658eff3307ad595f175f2624a3acfa8c Signed-off-by: David Wagner <david.wagner@intel.com>
* Introduce Python bindingsDavid Wagner2015-01-286-0/+407
These bindings for the parameter-framework generic connector use "SWIG" to generate: - a C++ file providing a basic bridge between C++ and Python (must be compiled to a shared library named "_PyPfw.so" - the name is important) - a Python module wrapping it inside a Proxy class, re-creating the same classes as the parameter-framework generic connector. See http://www.swig.org for the full SWIG documentation. They are generated and compiled on-the-fly as part of the build process. Change-Id: If7c67f1178dcc9f438cf037246eb77bbd74b689a Signed-off-by: David Wagner <david.wagner@intel.com> Signed-off-by: Sebastien Gonzalve<sebastien.gonzalve@intel.com>