[riot-notifications] [RIOT-OS/RIOT] sock: expose configuration file (#11561)

Martine Lenders notifications at github.com
Wed May 22 12:03:34 CEST 2019


AFAIK it doesn't has to be. The important thing is that it is within a doxygen group (which doesn't has to be in its own file). IIRC for gcoap we did it like that.

> Isn't the important change to prefix the defines with CONFIG_?

I'm not sure this is anymore this is a sensible, scalable change. Just take `pkg` for an example: Technically they contain compile-configuration for RIOT. Exposing them all as `CONFIG_…` provides a huge maintenance burden for us. So why not find a more unified way to expose/document/configure them? Let's discuss this further in #10566, however.

-- 
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/pull/11561#issuecomment-494738577
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190522/762acb4c/attachment.html>


More information about the notifications mailing list