Skip to content
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

Allow for overriding the normal tool/builder lookup #88

Open
jimporter opened this issue Mar 13, 2017 · 0 comments
Open

Allow for overriding the normal tool/builder lookup #88

jimporter opened this issue Mar 13, 2017 · 0 comments
Labels
Milestone

Comments

@jimporter
Copy link
Owner

For some niche use cases, it might be useful to override the normal tool/builder for a particular case. For instance, maybe you want to build most of your stuff with gcc, but you want to use icc for one build. Or build with gcj but run a "regular" Java program.

One possible implementation is this:

  • Add some optional arguments to env.tool() and env.builder() that produce non-cached tools/builders; you'd probably want to do this by overriding env vars
  • Let build steps take a builder argument (or compiler, linker, etc) that overrides the default builder selection
  • Either make it easy to explicitly use run-wrappers or provide a way to override the runner/"builder" when running commands
@jimporter jimporter added this to the future milestone Mar 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant