[riot-notifications] [RIOT-OS/RIOT] Define requirements for configuration in the build system (#14027)
notifications at github.com
Thu May 7 10:25:54 CEST 2020
Regarding avoiding cyclic dependency, I think we all can agree that it would be great to avoid them. I also think it is technically possible. The question is about the magnitude of work to correct this. Maybe it is just a matter of using an `#ifdef` around all the places such as the `Hello! this is RIOT` print or breaking it down into finer granularity such as a `core` and `core_with_hello`, in which case I would say let's start the work now. I have usually found that it is not as easy as that, however, I still think that we get some great advantages for everyone that would make the struggle worth it.
A concern that I have is regarding integration with things outside RIOT.
If I have an application that uses RIOT and some third-party stack, and that third-party stack has some circular dependencies (or violating the other requirements for that matter), does this pose a problem, or is it only within RIOT that we would have this requirement?
Aside from that, I agree with this idea, not only does this improve the quality and design of RIOT but also allows for tools to take advantage of a defined structure (more projects, more work :smiley:)
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