[riot-notifications] [RIOT-OS/RIOT] riotboot: add riotboot_bootloader pseudomudule (#12307)

Gaëtan Harter notifications at github.com
Fri Sep 27 10:44:34 CEST 2019

If you think `APPLICATION` is a variable than can be used to configure any different behavior of the build, please document this in `makefiles/vars.inc.mk` for consistency.

But as CFLAGS (not even considering evaluating CFLAGS can slow down the build), it goes for me against the dependency inversion principle, but as I will not maintain it is your choice

My issue with doing something with "it's the bootloader", is that then the behavior is not triggered by enabling a feature, or a module, but enabled even when not needed except when we disable it after.
I prefer only add things than blacklist for configuration.

If only the feature `riotboot` is not enough to differentiate between a bootloader and an application, anymore, it needs another name. Similar to saying "I am a bootloader", but from the application side to not blacklist.
I would change that application that wants to be build for riotboot, should say `USEMODULE += riotboot_slot` or something (except that this one clashes with an existing module).

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...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190927/5704a516/attachment.htm>

More information about the notifications mailing list