Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: Iea1bb66bb3aea8a120e7bbb3b55895682044cf23
Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
|
|
Change-Id: I0fa96d14d42d1ef80eb0340f48a644c378d4dcbe
Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
|
|
Change-Id: Ib67fab1ecd5085e089769e7905cd5ebcd28b9c7c
Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
|
|
Instead of specifying a JSON configuration file with CAN devices name, it uses
a mapping configuration file that map a high level device names to a real low level names.
File path is to be specified into the generated source code which is /etc/dev-mapping.conf
for now.
Configuration file uses INI file format and is parsed using inih library cpp wrapper.
Change-Id: Ibde104e76cd78a6cc86f6eec4f66c274b7567d43
Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
|
|
Each projects, binder and generator, has to be compiled separatly.
CAN-binder will host high and low level binding
CAN-config-generator only the generator used for low level binding.
build.sh script just launch both build in their respective dir.
Change-Id: Ic77932660fcca507b23a631d4e4e790f608880ae
Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
|