ConstraintsΒΆ

For new platform and middleware software, the following constraints are applicable.

  • Components shall be implemented in C or C++, unless there is a good reason for choosing another language.

  • Software which is implemented in C++ shall follow the AUTOSAR C++14 guidelines.

  • D-Bus shall be the preferred IPC for control data, unless there is a good reason for choosing another IPC.

  • D-Bus related software shall use GDBus as client library and it's recommended to use gdbus-codegen-glibmm, which generates C++ D-Bus stubs and proxies using Giomm/Glibmm.

The preferred IPC mechanism for dynamic content, i.e. applications, the SoftwareContainer approach shall be used. Currently, the following IPC gateways are supported:

  • Screen access

  • Audio access

  • D-Bus filter per service and interface

  • Device node access

  • Unix domain socket access

  • Writable system mount and persistence strategy