Skip to content

Conversation

@betaboon
Copy link
Collaborator

@betaboon betaboon commented Feb 1, 2025

supersedes #104

[`toolchains_llvm`][1] only triggers its logic to locate files relative
to the compiler wrapper when called with an absolute path, for example.
Otherwise it assumes it's being called from the bazel execroot, which is
not true in this case.

`toolchains_llvm` already has similar logic as `wheel_builder` for
mapping paths, which could be used by just calling it with an absolute
path instead of using `wheel_builder`'s wrapper, but I think it's easier
to use the `wheel_builder` version instead of trying to detect whether
the toolchain has this logic.

[1]: https://github.com/bazel-contrib/toolchains_llvm/blob/1d685a99db5f1e6523c392e7dfaced583062cbc4/toolchain/cc_wrapper.sh.tpl#L37
@betaboon betaboon marked this pull request as ready for review February 1, 2025 10:43
@betaboon betaboon force-pushed the absolute-cc-compiler-path branch from 08454ab to dada472 Compare February 1, 2025 11:55
@betaboon
Copy link
Collaborator Author

@jvolkman as you had some opinions in #104 i'd like your opinion on this PR :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants