[riot-notifications] [RIOT-OS/RIOT] boards: examples: tests: refactor the way boards providing netif is used (#11676)

Alexandre Abadie notifications at github.com
Wed Jun 12 08:44:56 CEST 2019


I think the best would be to put the `FEATURES_REQUIRED += netif` (or `radio_xxx`) at a lower level than board level. I would say in a `Makefile.features` at driver level, but these files doesn't exist (yet).
This way when a driver module is loaded, the build system knows the features provided by this driver. If it's at86rf2xx, it would be netif, radio_802154 for example.
Like this, it will then be possible to add `PERIPH_REQUIRED += netif` as a dependency of `netdev_default` or `gnrc_netif` without having to touch the boards.

-- 
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/11676#issuecomment-501142701
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190611/1d19a767/attachment.html>


More information about the notifications mailing list