Add bazel query flag to work around bug #414
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mmdriley
approved these changes
Mar 23, 2021
| @@ -71,6 +71,7 @@ | |||
| "query", | |||
| "--keep_going", | |||
| "--output=location", | |||
| "--incompatible_display_source_file_location", | |||
There was a problem hiding this comment.
let's leave a comment to warn our future selves about this sharp edge
chandlerc
pushed a commit
that referenced
this pull request
Jun 28, 2022
Add Bazel query flag to work around bazelbuild/bazel#8900
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Due to a bug,
--output=locationsdoes not behave as specified in some versions of Bazel, with the result that the generatedcompile_commands.jsoncontainsBUILDfiles in place of all non-generated C++ source files. This is fixed in Bazel 4.0.0, but only behind the--incompatible_display_source_file_locationflag.