*/Makefile.dep: remove usage of DEFAULT_MODULE += stdio%#13791
*/Makefile.dep: remove usage of DEFAULT_MODULE += stdio%#13791aabadie merged 2 commits intoRIOT-OS:masterfrom
Conversation
31f2287 to
eeef8b5
Compare
|
The build is failing for |
Isn't soft device due for deprecation anyway, I can patch this until deprecation by adding |
943ed2e to
3f0357c
Compare
|
Any suggestions on where I could define |
maribu
left a comment
There was a problem hiding this comment.
ACK. I have one inline comment. Please squash that right in, if you choose to take this comment.
|
It would be good to have one more round of Murdock, now that #13349 is merged. They should not have any interactions and everything should still be fine. But if there is one thing I learned in the last few days, it is being careful with assuming what will/won't break the build process in possibly subtle ways. (If you take the comment, that rebuild would happen any, so I resist toggling the label for now.) |
efb0902 to
98d20fa
Compare
nrf52 includes include $(RIOTBOARD)/$(BOARD)/Makefile.dep to know if `nordic_softdevice_ble` is used, this changes dependency resolution sinnce -include $(APPDIR)/Makefile.board.dep should be resolved before. This can be removed once RIOT-OS#9913 is if `nordic_softdevice` is deprecated.
98d20fa to
72a2220
Compare
|
Addressed both comments and squashed. |
|
I'm also OK with this PR. The current position of Let's go with this one, ACK |
Contribution description
This PR removes all usage of
DEFAULT_MODULE += stdio_%. When this was added it was to make explicit an implementation choice, from allstdio_modules which one to use in an application.Using
DEFAULT_MODULEmade the "preferred" choice clear, and also allowed for applications or applications requirements to change the preferred one.This seemed like a good choice at the time because
DEFAULT_MODULEand the issues with its recursive expansion where not properly understood. This leads to a lot of weird corner cases, comments in #13651 have been in the direction of simply removing that kind of usage. In #13785 I had included a temporal exception forstdio_until something like #13469 (comment)_ or as a result of #13469.But know I think this is already causing more harm than good, because its poorly understood and also causes issues in
info-boards-supportedwhere recursive expansion ofDEFAULT_MODULEdoesn't happen.Maybe the declaration of
STDIO_MODULEScan be moved earlier?PS: @miri64 and @haukepetersen had spoken against this before, but we didn't understand
DEFAULT_MODULEs issues at the time, there gut feeling seemed to be right.Testing procedure
green murdock (lets see if issues stop popping up :))
test on
BOARDthat used to declareDEFAULT_MODULE += stdio_%The "default" is still excluded when needed to be.
Issues/PRs references
Related to #13651 #13469
Introduced in #12724