Generate afm-unit.conf using m4
authorJosé Bollo <jose.bollo@iot.bzh>
Wed, 15 Nov 2017 15:20:28 +0000 (16:20 +0100)
committerJosé Bollo <jose.bollo@iot.bzh>
Fri, 24 Nov 2017 16:44:57 +0000 (17:44 +0100)
commit88531199d2f46f8758dd1ef3262e567cc849c0b8
tree610ecc205121ddd7421755e07be878901830ed73
parent597a0e00c4fcb1af745804be6249f08203084f62
Generate afm-unit.conf using m4

The use of m4 to generate the afm-unit.conf and
afm-unit-debug.conf files has benefits:

 - the sync between debug versus not debug is mechanical

 - it allows easier maintainance by improving readability
   and writability (ex: macros TARGET or UNIT_NAME_BASE)

Change-Id: Ic0427bedf4f8a5b174318562336603077f174fa5
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
conf/afm-unit-debug.conf.in
conf/afm-unit.conf.in
conf/generate-unit-conf/Makefile [new file with mode: 0644]
conf/generate-unit-conf/afm-unit [new file with mode: 0644]
conf/generate-unit-conf/binder.inc [new file with mode: 0644]
conf/generate-unit-conf/provided.inc [new file with mode: 0644]
conf/generate-unit-conf/service.inc [new file with mode: 0644]