chore: add .bazelignore to fix some build failures #1268
Merged
Conversation
This file contains hidden or 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
If you have build using CMake following the build instructions in the README, and then you subsequently try to build everything (`//...`) with bazel without first cleaning the CMake output, then the bazel build fails. This is because the CMake build (when following the README) pulls down googletest (and maybe other things?) into the build/ directory, which means there are random BUILD files under build/, and bazel will find these and try to use them as part of the module. So ignore a 'build' directory.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
If you have build using CMake following the build instructions in the README, and then you subsequently try to build everything (
//...) with bazel without first cleaning the CMake output, then the bazel build fails. This is because the CMake build (when following the README) pulls down googletest (and maybe other things?) into the build/ directory, which means there are random BUILD files under build/, and bazel will find these and try to use them as part of the module.So ignore a 'build' directory.
Also ignore the examples/bazel directory, since that is explicitly an example of how to use jsonnet from a separate bazel module.