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

José Alamos notifications at github.com
Thu May 7 11:34:54 CEST 2020

> 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?

Just a side note: I think we should distinguish between "cooking"/configuring the RIOT kernel and linking third parties libraries. AFAIS the requirements cover the former.

Some libraries (in shape of PKGs) are configured via the RIOT build system because there's some "kernel contrib code" that might require different configurations. For instance, the OpenThread integration exposes some configuration options that might be relevant to the contrib code. But the build system acts as an interface for the actual pkg configuration (e.g using the `openthread-ftd` module injects some CFLAGS and `./configure` options to OpenThread's cmake).

But in general, third-parties will use their own build system. Thus, linking third party libraries is indeed in the scope of "RIOT Build System" but out of the scope of the having cyclic/acyclic graphs

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/20200507/677afb09/attachment.htm>

More information about the notifications mailing list