Udev rules are installed by our scripts/Makefile
as they are specific to our project

udev rules and custom scripts were reverted
and those need to be install from bpm-sw repository

In this was all of our services have the same
name independent of the init system

This was used in the past when the hotplug
was not working. So, we needed a manager
to spawn our daemons when a new board was
detected

Later this must be generic so other apps
can use the same script

This could be overrided to the desired BPM instance

Later this must be generic so other apps
can use the same script

Later this must be generic so other apps
can use the same script

Now, when adding a new application (e.g., Photon BPM)
we just need to add a new folder inside src/apps and
adjust the src/apps/<app_name>/<app_name>.mk Makefile

Now, almost all (with the exception of the dev_io.c which
will be fixed soon) specific code to a board is
located inside include/board/<board_name> and
src/board/<board_name>

Hotfix: building with clang
Hotfix: unused variable on some compilation options

Version v0.2.1

Clang does not understand the -T option.

As this is used only by the linker, use
-Wl option to pass options directly to the
linker in use.

The client_cfg variable was unused in some cases
(e.g., not AFCv3 board or not with DEVIO_CFG).
This caused an error on compilation for legacy
boards.

Version v0.2

We need to wait a little after creating DEVIO
CFG. Without that, malamute does not seem to
transmit the liblcient messages after the DEVIO
CFg is created. To be investigated, but this
simple fix works.

RFFE DEVIO already has the correct slot number
from the regular DEVIO. As such, it does not need
to spawn a libclient instance to get ther board
number from DEVIO CFG.

This simplifies the creataion/destruction of DEVIO
CFG, as we don`t need to wait for anything to destroy
it. The regular DEVIO just kills it after getting the
board number.

This fixes #94 github issue.