Google Git
Sign in
android / platform / build / c5255203c7
commitc5255203c7818ac6cc7bcfa229ba26560c8dffc6[log] [tgz]
authorGurpreet Singh <gurpreetgs@google.com>Fri Sep 08 13:23:41 2023 +0000
committerCherrypicker Worker <android-build-cherrypicker-worker@google.com>Mon Sep 11 14:38:42 2023 +0000
tree49f3bbc2d90f218c8b67ee65ce9dcab5b5a262a5
parente30a7397580405e509a60c4aa257c3e6731f1e0f [diff]
Add OWNERS for sdk extensions version updates

Our team performs the mainline sdk releases and has to update the sdk
extensions version on every release.

Adding people who are involved in the sdk ext release process so that
changes related to sdk extensions version updates can be approved by
our team.

We will only be approving changes which updates sdk extensions version.

Bug: N/A
Test: N/A
(cherry picked from https://android-review.googlesource.com/q/commit:3b3e686d8bd21d522b77568357efdb6589ac13b3)
Merged-In: I42755dbae7054161f56e789b57e064084eebc7c7
Change-Id: I42755dbae7054161f56e789b57e064084eebc7c7
1 file changed
tree: 49f3bbc2d90f218c8b67ee65ce9dcab5b5a262a5
  1. common/
  2. core/
  3. packaging/
  4. target/
  5. tests/
  6. tools/
  7. .gitignore
  8. banchanHelp.sh
  9. buildspec.mk.default
  10. Changes.md
  11. CleanSpec.mk
  12. Deprecation.md
  13. envsetup.sh
  14. help.sh
  15. METADATA
  16. navbar.md
  17. OWNERS
  18. PREUPLOAD.cfg
  19. rbesetup.sh
  20. README.md
  21. shell_utils.sh
  22. tapasHelp.sh
  23. Usage.txt
README.md

Android Make Build System

This is the Makefile-based portion of the Android Build System.

For documentation on how to run a build, see Usage.txt

For a list of behavioral changes useful for Android.mk writers see Changes.md

For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.

This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.