The main README (https://github.com/w3c/automotive-viss2#vss-tree) contains some text that is not really up to date. It refers to GENIVI rather than COVESA and command like make cnative is no longer supported by vss/vss-tools. Is it possibly the binary format it refers to? It is also not clear where the server_core directory is.
_The vehicle signals that the W3C VISS v2 server manages are defined in the "vss_W3C VISS v2.cnative" file in the server_core directory. New cnative files containing the latest verision on the VSS repo can be generated by cloning the Vehicle Signal Specification repo, and then issuing a "make cnative" command, see Tools usage._
UlfBj
commented
1 year ago
The main README (https://github.com/w3c/automotive-viss2#vss-tree) contains some text that is not really up to date. It refers to GENIVI rather than COVESA and command like
make cnativeis no longer supported by vss/vss-tools. Is it possibly the binary format it refers to? It is also not clear where theserver_coredirectory is._The vehicle signals that the W3C VISS v2 server manages are defined in the "vss_W3C VISS v2.cnative" file in the server_core directory. New cnative files containing the latest verision on the VSS repo can be generated by cloning the Vehicle Signal Specification repo, and then issuing a "make cnative" command, see Tools usage._