[riot-notifications] [RIOT-OS/RIOT] Define requirements for configuration in the build system (#14027)

Leandro Lanzieri notifications at github.com
Wed May 6 13:36:57 CEST 2020


> For example, everything outputting something depends on stdio_X (usually stdio_uart). Even core ("Hello! this is RIOT."). But stdio_uart also depends on core (it uses isrpipe, which uses mutex, ...). So core does not link without stdio_X. But stdio_x does not link without core. That is a cyclic dependency. IMO, it is "valid".
> 
> Can that be modeled differently? Probably. But would that make sense? How would that look?

Regarding the message in `core_init`, couldn't the strong dependency be avoided if the message is only printed when an `stdio_x` is present? Similarly to the call to `auto_init`:
```C
#ifdef MODULE_AUTO_INIT
    auto_init();
#endif

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/issues/14027#issuecomment-624597887
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20200506/8954ae19/attachment.htm>


More information about the notifications mailing list