-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Labels as tool_path
in CROSSTOOL
#7642
Comments
As of bazel 0.23.0 CROSSTOOL is deprecated in favour of skylark cc_toolchain and cc_common.create_cc_toolchain_config_info. See here. However the same problem persists in the new implementation i.e. tool_path(
name = "gcc",
path = "@some_gcc//bin:gcc",
), Is not possible. I would perhaps recommend editing the CROSSTOOL title to this issue to match the new toolchain skylark api, as it is more likely to receive support. |
I am also interested in a fix or a workaround for this. I would be happy to create a more up to date descriptive issue if that were ok with you? |
Sure. I can not edit title from phone unfortunately. |
I have added a new issue here #7746. If this doesn't cover your use case I'd keep this issue open. |
[``](**### **) |
#700# |
cc/ @hlopko |
Hi all, let's continue the discussion in #7746. Thanks! |
Can we have a possibility to specify Labels as
tool_path
inCROSSTOOL
's (possibly even being compiled in the same build)? That would be a great step towards hermeticness.E.g.:
The text was updated successfully, but these errors were encountered: