Small build system updates, make RIOT_USEMODULE optional#39
Merged
Conversation
This has been causing warnings all over the place, just because it was a marker variant that was currently not in use. As no markers will be added any more as per the deprecation note, this can go already.
This is not a breaking change, it just turns what used to be a build.rs error into a later error (eg. when used with an older riot-wrappers, that would be missing modules -- but only if the build system suddenly stopped passing in the variable). Tolerating the absence allows the build system to phase out passing dummy values into RIOT_USEMODULES even before [38] is through. [38]: #38
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
These are the non-breaking parts of #38.