Fix wscript support#966
Merged
Merged
Conversation
The waf build system uses "wscript" files, whereby "wscript" is the
actual file name and not an extension ("foo.wscript" is not supported).
wscript files are normal Python files.
Owner
|
If |
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
2 participants
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.
The waf build system uses "wscript" files, whereby "wscript" is the actual file name and not an extension ("foo.wscript" is not supported). wscript files are normal Python files.
See also https://waf.io/book/#_waf_commands_and_usage
I'm unsure if wscript should be moved from Language_by_Extension to Language_by_File_Type vs just added to Language_by_Extension, because e.g. Makefile and other names are listed in both places too.