Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / 9008724b50e8ce8d3582ec31487bf35079d6d08a
commit9008724b50e8ce8d3582ec31487bf35079d6d08a[log] [tgz]
authorMårten Kongstad <amhk@google.com>Tue Apr 16 09:55:56 2024 +0200
committerMårten Kongstad <amhk@google.com>Tue Apr 16 10:32:17 2024 +0200
tree639c5381f874fa113e2ba7c9d86edfb141d21355
parentf2b6a44b064c8ecec1db1eeb830b4bc9526c8952 [diff]
check-flagged-apis: add new CLI to verify @FlaggedApi APIs

Add a new CLI to verify that the build artifacts contain the right set
of @FlaggedApi APIs, based on the value of the corresponding aconfig
flag.

This CLI will act as an end-to-end test of Soong and metalava.

This CL only adds the project scaffolding; later CLs will add the
implementation.

Bug: 334870672
Test: m check-flagged-apis && check-flagged-apis
Change-Id: Ib00653f2a549217da2b0058867c711f35efd5760
4 files changed
tree: 639c5381f874fa113e2ba7c9d86edfb141d21355
  1. ci/
  2. common/
  3. core/
  4. packaging/
  5. target/
  6. teams/
  7. tests/
  8. tools/
  9. .gitignore
  10. banchanHelp.sh
  11. buildspec.mk.default
  12. Changes.md
  13. CleanSpec.mk
  14. cogsetup.sh
  15. Deprecation.md
  16. envsetup.sh
  17. help.sh
  18. METADATA
  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.