Marcel Hlopko
Marcel Hlopko
cc @fweikert @philwo
For the reference, https://github.com/bazelbuild/rules_go/blob/master/tests/bazel_tests.bzl#L331 is the place where rules_go try to find Bazel binary. Bazel CI currently doesn't set BAZEL environment variable so this logic is incorrect when running on...
Good idea! I'll do that.
With https://buildkite.com/bazel/rules-cc-plus-bazelisk-migrate it will be easier to keep track of incompatible changes.
Some old but related doc on the topic of more constraint settings: [docs.google.com/document/d/1CgU-GKocMAfsUSI3bbGZ0YRkOWczitIoKs29x3zR914/edit#heading=h.3fbh1otqm5sz](https://docs.google.com/document/d/1CgU-GKocMAfsUSI3bbGZ0YRkOWczitIoKs29x3zR914/edit#heading=h.3fbh1otqm5sz)
Why do you create your own static library action? Sandwich api will create one if needed. Also, I could be convinced to have that function here in this repo, but...
I'm sorry you had to struggle through this without proper docs. Docs will be provided for the stable API, but because the experimental API was changing a lot it didn't...
I'm investigating the UIKit issue.
Yay for surprises :) So the osx C++ toolchain doesn't yet work with platforms because of this [TODO](https://source.bazel.build/bazel/+/8bd7e4822ed96615ccac77cc40ca96eddc74c510:tools/osx/crosstool/BUILD.tpl;l=89). @katre kindly volunteered to fix it :)
@nlopezgi In the error message I see `cc_toolchain_suite`, that shouldn't be used at all with `--incompatible_enable_cc_toolchain_resolution`, is it possible that you were building the `cc_toolchain_target` explicitly? The expected error message...