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

Route "compiler" value of config_setting through @bazel_tools/tools/cpp:compiler. #5085

Merged
merged 2 commits into from
Sep 10, 2018

Conversation

scentini
Copy link
Contributor

No description provided.

@xfxyjwf xfxyjwf self-assigned this Aug 29, 2018
@xfxyjwf xfxyjwf added the bazel label Aug 29, 2018
@xfxyjwf
Copy link
Contributor

xfxyjwf commented Aug 29, 2018

Can you point me to some documentations about this change in bazel?

laszlocsomor added a commit to laszlocsomor/bazel that referenced this pull request Sep 4, 2018
See protocolbuffers/protobuf#5085

Change-Id: I1253bd78388f14bac78e01841cfcdb6b72c8860b
@scentini
Copy link
Contributor Author

scentini commented Sep 4, 2018

Sorry for the delayed reply,

We are rerouting how the 'compiler' value is accessed in Bazel, which is a backwards incompatible change:
https://docs.bazel.build/versions/master/skylark/backward-compatibility.html#disable-late-bound-option-defaults

I combined the old and the new way of dealing with 'compiler' in a compiler_config_setting.bzl file so it stays backwards compatible.

@xfxyjwf xfxyjwf merged commit ff3891d into protocolbuffers:master Sep 10, 2018
anandolee pushed a commit that referenced this pull request Nov 21, 2018
* use flag_values = {"@bazel_tools//tools/cpp:compiler": "x"} for compiler config_settings

* Create compiler_config_setting.bzl
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants