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

Kaspar Schleiser notifications at github.com
Wed May 6 12:01:55 CEST 2020

> Sorry, I still have to disagree on this point. What would be a valid circular dependency? And what do we gain from that?

Well, this is just how our code is laid out. 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?

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/20200506/a4d89c4b/attachment.htm>

More information about the notifications mailing list