dawagner / parameter-framework / 280
0%
master: 78%

LAST BUILD BRANCH: integerparam-template
DEFAULT BRANCH: master
Ran
Jobs 2
Files 233
Run time 39s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
280

push

travis-ci

dawagner 
Rework the plugin entry-point API to be a well-known symbol name

The plugins' entry-point used to be a symbol which name was constructed based
on the library name but the Parameter Framework was trying to deduce it based
on how library files are usually named on Linux, i.e. prefixed with "lib", then
the soname, then ".so".

This is not always true on Linux and this is usually false on Windows.

Also, if the API of this symbol changes, there is no way to know at
compile-time.

Which is why this rework introduces a macro to be used by plugins. This macro
is the name of the entry-point symbol to be declared by plugins and will be
retrieved by the Parameter Framework.

If the plugin entry point API changes, we will change the name of the macro
(it contains a version number), which will cause the plugins to raise an error
at compile time instead of failing at runtime.

For now, we only support one API version at a time: if the API changes from V1
to V2, the plugins won't compile and the Parameter Framework won't recognize
previously-compiled plugins using V1. If we want backward-compatibility, we can
add it later by declaring both macros (V1 and V2) and trying to find the symbol
corresponding to V1 if the symbol corresponding to V2 can't be found.

The first name of the macro is: PARAMETER_FRAMEWORK_PLUGIN_ENTRYPOINT_V1

Signed-off-by: David Wagner <david.wagner@intel.com>

4805 of 6618 relevant lines covered (72.61%)

3461.43 hits per line

Jobs
ID Job ID Ran Files Coverage
1 280.1 0
72.61
 Travis Job 280.1
2 280.2 0
0.0
 Travis Job 280.2
Source Files on build 280
Detailed source file information is not available for this build.