-
-
Notifications
You must be signed in to change notification settings - Fork 649
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Associate cli arguments with executables and refactor llvm/gcc c/c++ toolchain selection #6217
Merged
cosmicexplorer
merged 24 commits into
pantsbuild:master
from
cosmicexplorer:refactor-llvm-gcc-toolchain-selection
Jul 24, 2018
Merged
Changes from 1 commit
Commits
Show all changes
24 commits
Select commit
Hold shift + click to select a range
f330514
introduce CToolchain and CppToolchain to pair related tools
cosmicexplorer 9e36cd0
make the rest of the native backend subsystem testing work
cosmicexplorer b0e7b52
make python_dist() compilation work with the new native backend
cosmicexplorer 8193ca9
fix python dist integration tests
cosmicexplorer 1c0c880
move argument generation into the executable objects themselves
cosmicexplorer 6e3bcbc
make everything work on osx
cosmicexplorer 9a16efb
remove/update TODOs/FIXMEs
cosmicexplorer 2bc7698
remove unnecessary `RootRule`s
cosmicexplorer 900a476
refactor ParseSearchDirs
cosmicexplorer 78fe179
add FIXME
cosmicexplorer e67044c
refactor gcc subsystem to use globs instead of guessing platform-spec…
cosmicexplorer 3441e74
remove GCCCCompiler, GCCCLinker, etc
cosmicexplorer 6843579
inject CToolchain and CppToolchain and select which with other @rules
cosmicexplorer b2a750b
centralize -mmacosx-version-min=10.11 argument creation
cosmicexplorer 973f26e
clarify some comments on the clang args we add
cosmicexplorer 3051235
split off indexing into BinaryTool archives using the new ArchiveFile…
cosmicexplorer 09526d2
remove -nostdinc from clang args
cosmicexplorer 8f34e37
make searching gcc BinaryTool paths work on osx
cosmicexplorer 8fd7baa
fix up docstring formatting
cosmicexplorer e5a5d7e
add the environment to the compiler or linker invocation so we can re…
cosmicexplorer f4a8a7d
only add --gcc-toolchain argument to clang and clang++ on linux
cosmicexplorer 9846475
remove all python backend rules
cosmicexplorer 7ebfe51
remove TODO in SetupPyExecutionEnvironment
cosmicexplorer ac543fe
remove CToolchain/CppToolchain rules and add explanatory comment in e…
cosmicexplorer File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have you been able to verify that setup.py compilation is taking place with the correct exe? I recall we hit some cases where it wasn't actually respecting this variable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With the correct
exe_filename
? There is no testing that the setup.py compilation does anything other than succeed, currently, but if you make the build fail (e.g. by inserting a syntax error into a C/C++ source), pex will print the stdout and stderr to the terminal stderr, and you can see that modifyingexe_filename
s (or e.g. selectingGCCCToolchain
instead of the llvm one inpython_native_code.py
) will change the compiler used for the generated command line to build setup.py native sources.At this point, I'm not sure what we should be testing wrt setup.py compilation other than success. If you have some itches you want to scratch, an issue just listing what tests we should add, or a PR doing that, would be great so I or someone else can address it in full. This wouldn't need to more than a few sentences.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And that may have been the case (wrt not respecting
CC
), but I don't remember the situation, and the issue may have been e.g. that we were adding the wrong entries to thePATH
.