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

Thomas C. Schmidt t.schmidt at haw-hamburg.de
Fri Dec 1 13:01:56 CET 2017

Hiho Gaetan,

wasn't it in particular that the current build system does not produce 
well-defined results in the sense that the outcome depends on the order 
and hidden interferences??

Wasn't it also that the current configuration system includes overloaded 
semantics and is thus rather intransparent??

These to me seemed to be the core issues??


On 30/11/2017 22:27, Kaspar Schleiser wrote:
> Hi,
> On 11/30/2017 04:32 PM, Gaëtan Harter wrote:
>>        1. Configuration is not documented
>>        2. Information is not readable
>>        3. Modules definition is scattered but in RIOT global files
>> With these issues in mind, I propose to add parseable module meta-data
>> definitions in a file in each module directory to first replace the
>> existing information and then extend it to add more precise ones.
>> How to do in practice it is still to be defined and discussed.
> When are you gonna take a look at my ninja-based build system? It solves
> 1-3 quite nicely, and more. You could save a lot of time.
> Kaspar
> _______________________________________________
> devel mailing list
> devel at riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel


Prof. Dr. Thomas C. Schmidt
° Hamburg University of Applied Sciences                   Berliner Tor 7 °
° Dept. Informatik, Internet Technologies Group    20099 Hamburg, Germany °
° http://www.haw-hamburg.de/inet                   Fon: +49-40-42875-8452 °
° http://www.informatik.haw-hamburg.de/~schmidt    Fax: +49-40-42875-8409 °

More information about the devel mailing list