Closed mikehaller closed 1 year ago
Proposed recipe structure:
Existing .../recipes-sdv/eclipse-kuksa/ - databroker-vss-core <- https://github.com/eclipse/kuksa.val/tree/master/data/vss-core (*.json)
New .../recipes-sdv/covesa/ - vss-releases.bb (*.vspec)
New .../recipes-sdv/covesa/ - vss-tools.bb <- https://github.com/covesa/vss-tools/
Propose to have them installed as native recipes, as it seems to be easy to do.
The tooling to convert VSS vspec files into various formats and the VSS specification itself should be available on the quickstart image pre-installed.
It is easy to install later, if you have connectivity and git installed (which is not the case). However, if we want to prepare an environment where you can easily customize the vehicles data model, the databroker container would also be affected.
Hence, there are configurations like the global VSS datamodel which can be customized and is required by multiple software packages.
Request:
Example setup includes databroker with custom vss plus the dbc2val feeder which also requires the model.
It is also worth checking out if certain DBC related tools should be preinstalled. Alternatively, ae may use vss-tools container, if such a thing exists.