Skip to content

Allow passing env to cc_tool#598

Open
dzbarsky wants to merge 1 commit intobazelbuild:mainfrom
dzbarsky:zbarsky/tool-env
Open

Allow passing env to cc_tool#598
dzbarsky wants to merge 1 commit intobazelbuild:mainfrom
dzbarsky:zbarsky/tool-env

Conversation

@dzbarsky
Copy link
Contributor

@dzbarsky dzbarsky commented Feb 8, 2026

This covers 2 use cases:

  1. passing license file env vars to proprietary compilers
  2. Exposing the location of helper binaries to cc_tool. The alternative of supplying those as env/data via cc_args doesn't work because then the binaries will be cfg=target instead of cfg=exec.

@trybka
Copy link
Collaborator

trybka commented Feb 9, 2026

@armandomontanez any thoughts as SME for rules-based Toolchains?

@dzbarsky
Copy link
Contributor Author

dzbarsky commented Feb 9, 2026

@armandomontanez any thoughts as SME for rules-based Toolchains?

Sorry should have shared the context, this was Armando's suggestion :) https://bazelbuild.slack.com/archives/CGA9QFQ8H/p1770220066174189?thread_ts=1770153962.810599&cid=CGA9QFQ8H

@armandomontanez armandomontanez added type: feature request Request for new, generally useful functionality that is missing P2 We'll consider working on this in future. (Assignee optional) category: toolchains labels Feb 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

category: toolchains P2 We'll consider working on this in future. (Assignee optional) type: feature request Request for new, generally useful functionality that is missing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants