dist/tools/buildsystem_sanity_check: add an export variable check#11484
Merged
jcarrano merged 1 commit intoRIOT-OS:masterfrom May 7, 2019
Merged
Conversation
a2e0a98 to
4c7b9be
Compare
Contributor
Author
|
I pushed force a line cleanup that stayed in my repository. Putting a fixup would still break the static tests that I would like to show they are passing. |
jcarrano
suggested changes
May 3, 2019
Contributor
|
Squash and we're done. |
Check that some variables are not exported in the build system. This should track variables that managed to not be exported anymore so that they do not reappear in a BSP. It is not a whitelist but just a way to keep things cleaned in the future.
0337f7a to
42b3cd5
Compare
Contributor
Author
|
Squashed :) |
Contributor
Author
|
Thanks for the review. Now we can start removing exported variables more easily :) |
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
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.
Contribution description
Check that some variables are not exported in the build system.
This should track variables that managed to not be exported anymore so
that they do not reappear in a BSP.
It is not a whitelist but just a way to keep things cleaned in the
future.
Testing procedure
No error when running the script as will CI check in
static-tests.No error when running
shellcheckon the script.Applying this diff will report a lot of errors as they are still exported.
I used
PORThere on purpose as it may need to be more complicated to not matchPORT_LINUXtoo. Even ifPORT_LINUXshould not be exported anyway but anotherPORTSOMETHINGmay need to.Issues/PRs references
Tracking: remove harmful use of
exportin make and immediate evaluation #10850Useful for #10440