Add Bazel support #605
Open
Add Bazel support #605
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
Vertexwahn
force-pushed
the
bazel-support
branch
3 times, most recently
from
dd798d2
to
6cac317
Compare
Vertexwahn
force-pushed
the
bazel-support
branch
from
6cac317
to
bbd7fcf
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
This PR helps users of the Bazel build system to integrate pugixml in their builds.
Supporting the Bazel build systems is of course more effort to maintain but helps to spread pugixml.
In the worst case the Bazel build path does simply not work - in the best case, someone who uses Bazel can benefit from it.
Also, other projects support Bazel side by side to other build systems (e.g. Catch2, gtest, etc.).
I will maintain the pugixml Bazel build at least for a half year.