| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Bug 246391
Change-Id: I662b7b0f90c97cb169978e1b64ad1fe32c440cf5
Signed-off-by: Jean-Michel Trivi <jmtrivi@google.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
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>
|
