get.py using .json tool name with git version #9155
Conversation
This file contains 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
renamed tools/xtensa-lx106-elf -> tools/xtensa-lx106-elf-gcc get.py can just use the top dir -> tool name translation, no need to ref archive contents. just expect top dir to be there
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.
Noticed while searching for 'import re' instances in python code.
Rename tool directory fetched with get.py into tool's actual name. Partially breaking for development builds, but here only lwip builder needs an update to reference tools/xtensa-lx106-elf-gcc instead.
Hopefully not breaking anything else.
Updated tools/xtensa-lx106-elf -> tools/xtensa-lx106-elf-gcc in the source and docs