[riot-devel] Updates to the build system - modules definition

Daniel Petry daniel.petry at fu-berlin.de
Fri Nov 24 16:47:29 CET 2017


Hi Gaetan


> I would like to introduce some packaging concepts around RIOT.
> To consider modules like well defined distribution packages and not only 
> source files added to an application firmware. 

>From what you're saying, I understand that the aim is to make modules
completely self-contained with respect to build definitions, and make
those definitions much more human readable.  In this way, an application
developer can go to only one place to find out information regarding a
module's build (dependency information, etc.), and a module developer
only has to write/change the module directory Makefile and can do so
with declarative language. Also, the information can be easily parseable
for eg a user interface.

So the changes you're proposing are:

1) Move build information concerning a particular module into that
module's Makefile
2) Make the module makefiles able to be written with purely declarative
language
3) Retain backwards compatibility with the current build system

Is this correct?

I think 2) would be great for user friendliness, and 3) is a no-brainer.
1) is a bigger topic as there are a number of different ways in which
dependencies are manifested for example, so I think this can be a point
for further discussion... do you have any particular examples?


Dan.



More information about the devel mailing list