Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / fe3c99c939ffaa8dbbc0bd222b3e47e449c8f257
commitfe3c99c939ffaa8dbbc0bd222b3e47e449c8f257[log] [tgz]
authorOwner Cleanup Bot <swarming-tasks@owners-cleanup-prod.google.com.iam.gserviceaccount.com>Thu Sep 12 17:48:06 2024 +0000
committerOwner Cleanup Bot <swarming-tasks@owners-cleanup-prod.google.com.iam.gserviceaccount.com>Thu Sep 12 17:48:09 2024 +0000
tree7afc6ddfd1a8d09746c39cbfd1e8985a3e61d19a
parent435145d063450a7e8df2df76f62a9d92a15dc96b [diff]
Remove jsharkey@google.com from core/OWNERS

This suggested change is automatically generated based on group
memberships and affiliations.
If this change is unnecessary or in error, vote the lowest CR value
(i.e. reject the CL) and the bot will abandon it. Vote the highest CR to
approve this change. You may also abandon this change.

See the owner's recent activity for context:
https://android-review.googlesource.com/q/jsharkey@google.com

To report an issue, file a bug in the Infra>Codereview component.

Change-Id: I07238816be1e959d04919abc10eac8c1024f7419
1 file changed
tree: 7afc6ddfd1a8d09746c39cbfd1e8985a3e61d19a
  1. ci/
  2. common/
  3. core/
  4. packaging/
  5. target/
  6. teams/
  7. tests/
  8. tools/
  9. .gitignore
  10. Android.bp
  11. banchanHelp.sh
  12. buildspec.mk.default
  13. Changes.md
  14. CleanSpec.mk
  15. cogsetup.sh
  16. Deprecation.md
  17. envsetup.sh
  18. help.sh
  19. navbar.md
  20. OWNERS
  21. PREUPLOAD.cfg
  22. rbesetup.sh
  23. README.md
  24. shell_utils.sh
  25. tapasHelp.sh
  26. 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.