[Genivi-ipc] Extending meta-ivi-test with a test that generates CAPI code during build

Konopelko, Pavel (P.) pkonopel at visteon.com
Thu Jun 9 13:40:56 EDT 2016

Hi Tolkien,

As discussed previously, I created a pull request for meta-ivi [1].  It includes three patches:

c55c45f common-api: introduce native recipes for core and dbus
4f0454f common-api: add capicxx-perf test
3c833bd common-api: introduce native recipe for someip

The last two patches (4f0454f and 3c833bd) can be applied on top of c55c45f independently.  The native recipes allow using Common API C++ generators as a part of the tool chain on the build host.  They rely on pre-built generators being available through the CAPIC++ update site.

The recipe capicxx-perf builds two executables (client and server) that rely on CAPIC++ with the D-Bus backend.  It invokes the code generators during the build and can be used to [smoke-] test both the CAPIC++ runtime and tools for core and D-Bus.

The recipe capicxx-someip-native can be optionally added to support SOME/IP code generator.  It is not required by capicxx-perf, though.

What do you think?

Please note that the proposed new recipes use the recently agreed naming convention [2] for Common API projects (which is unfortunately at odds with the one currently used by meta-ivi).  I would propose to align by adopting the names capicxx-core, capicxx-dbus and capicxx-someip for the corresponding CAPIC++ runtime component recipes.

Moving other existing CAPIC++ tests (built by common-api-test) will require more work in collaboration with the CAPIC++ maintainers and other interested parties (see e.g. [3]).  This can be done in separate steps.

--Pavel Konopelko

[1] https://github.com/GENIVI/meta-ivi/pull/1
[2] http://lists.genivi.org/pipermail/genivi-ipc/2016-May/000743.html
[3] http://lists.genivi.org/pipermail/genivi-ipc/2016-May/000736.html

Visteon Innovation & Technology GmbH 
Sitz der Gesellschaft: Kerpen  
Registergericht: Köln HRB 71036
Geschäftsführung:  Radboud Vaessen, Jens Tillner, Jürgen Dörr
CONFIDENTIALITY NOTICE: This e-mail message including attachments, if any, is intended only for the person or entity to which it is addressed and may contain confidential and /or privileged material. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient but do not wish to receive communications through this medium, please so advise the sender immediately.

More information about the genivi-ipc mailing list