docs: update README build and profiling instructions to use Bazel#110
Open
MohamedRady-99 wants to merge 1 commit into
Open
docs: update README build and profiling instructions to use Bazel#110MohamedRady-99 wants to merge 1 commit into
MohamedRady-99 wants to merge 1 commit into
Conversation
Change-Id: I735139d7dac6cb9087af54057a9a72697b61d97f
License Check Results🚀 The license check job ran with the Bazel command: bazel run //:license-checkStatus: Click to expand output |
|
The created documentation from the pull request is available at: docu-html |
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
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 resolves the issue with outdated README documentation by updating the build and profiling instructions to use Bazel instead of Cargo #70.
Since cargo build is no longer supported in this repository, and some previously referenced examples (like hello_tracing) do not have Bazel targets, the documentation has been rewritten to ensure all commands are fully functional with the current build system.
Proposal:
Currently, the documentation instructs users to build and profile using cargo and unsupported targets. This PR updates the workflow as follows:
Thanks!