[riot-notifications] [RIOT-OS/RIOT] Define requirements for configuration in the build system (#14027)
Thomas C. Schmidt
notifications at github.com
Thu May 7 11:52:45 CEST 2020
> E.g. if use of stdio in core would be optional and the build system would first build core (without message) and then stdio. Wouldn't it now have to build core again (with messages) this time? Or would the build system just rely on the fact that dependency cycles in C (and C++) with the headers are being available at any point in time and just build core with messages in the first compilation step?
This problem is only present if the built system is not aware of the entire configuration graph (as it is today). You are actually describing one of the current key problems of the RIOT build system, namely that it cannot produce uniquely defined, optimized targets. Rather, the results depend on the order of execution.
Whenever the build system can work on the basis of an exposed configuration graph, this problem disappears, which is one of the main goals of this work.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications