aboutsummaryrefslogtreecommitdiffstats
path: root/CAN-binder
AgeCommit message (Collapse)AuthorFilesLines
2017-04-18Use a system INI configuration file to get devices mappingRomain Forlot8-137/+84
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>
2017-04-14Fix: wrong testing command lineRomain Forlot1-1/+1
Missing rootdir option else binding can't find its configuration file Change-Id: I011d326dd27a5eae6f021080f08a82290200cc2c Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
2017-04-14Make name of virtual CAN device flexible.Romain Forlot1-2/+2
Change-Id: I9cef3e6c4fa81bb75514e7b9c618494bad00ab6a Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
2017-04-14Change directory architecture to use 2 separated projects.Romain Forlot83-0/+1618228
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>