Use a system INI configuration file to get devices mapping
authorRomain Forlot <romain.forlot@iot.bzh>
Tue, 18 Apr 2017 18:23:14 +0000 (20:23 +0200)
committerRomain Forlot <romain.forlot@iot.bzh>
Tue, 18 Apr 2017 18:23:14 +0000 (20:23 +0200)
commit44d7237fde80af222939445055a94a0e50e82935
treea65cd2e82fc70ddeed4fbf3b2cd05c4b025c8f90
parent3642f8f2545f22f2e574bbd820e67229516e9149
Use a system INI configuration file to get devices mapping

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>
.gitmodules
CAN-binder/libs/inih [new submodule]
CAN-binder/low-can-binding/CMakeLists.txt
CAN-binder/low-can-binding/can/can-bus.cpp
CAN-binder/low-can-binding/can/can-bus.hpp
CAN-binder/low-can-binding/configuration-generated.cpp
CAN-binder/low-can-binding/configuration.hpp
CAN-binder/low-can-binding/utils/config-parser.cpp
CAN-binder/low-can-binding/utils/config-parser.hpp