docs: add Bazel build instructions - #4
Closed
cw20050111-prog wants to merge 4 commits into
Closed
Conversation
Official docs previously only covered config_brpc.sh and CMake, leaving Bazel builders without guidance despite the repo already having full Bazel/bzlmod support. Add a "Compile brpc with bazel" section (build, run examples, run tests, and link to bazel_support.md for consuming brpc as a dependency) to both docs/en and docs/cn getting_started.md, with cross-reference links from the other OS sections matching the existing cmake pattern. Fixes apache#2991 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016u8i1npn8aMgNr5WiT97rt
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
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.
What problem does this PR solve?
Issue Number: Fixes apache#2991
Problem Summary:
The getting started docs describe building bRPC with
config_brpc.sh, CMake, vcpkg, and Docker, but they do not provide a Bazel build path even though the repository already contains Bazel and bzlmod support.What is changed and the side effects?
Changed:
//:brpc, building examples, running the echo example, and running Bazel tests.WORKSPACEusage documented separately.Side effects:
Performance effects: None. Documentation-only change.
Breaking backward compatibility: None.
Check List:
Note: this is a docs-only change. The existing CI workflows ignore
**.mdchanges, so CI may not be triggered automatically.