Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update build-rules.md #2355

Merged
merged 1 commit into from
Sep 11, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 2 additions & 10 deletions src/android/build-rules.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,16 +25,8 @@ Additional items speaker may mention:
- For compliance and performance, Android must have crates in-tree. It must also
interop with C/C++/Java code. Soong fills that gap.

- Soong has many similarities to Bazel, which is the open-source variant of
Blaze (used in google3).

- There is a plan to transition
[Android](https://source.android.com/docs/setup/build/bazel/introduction),
[ChromeOS](https://chromium.googlesource.com/chromiumos/bazel/), and
[Fuchsia](https://source.android.com/docs/setup/build/bazel/introduction) to
Bazel.

- Learning Bazel-like build rules is useful for all Rust OS developers.
- Soong has many similarities to [Bazel](https://bazel.build/), which is the
open-source variant of Blaze (used in google3).

- Fun fact: Data from Star Trek is a Soong-type Android.

Expand Down