Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / b9ce4c92e012e8a9a255d76aaa11b8df78930dee
commitb9ce4c92e012e8a9a255d76aaa11b8df78930dee[log] [tgz]
authorMårten Kongstad <amhk@google.com>Thu May 02 10:51:30 2024 +0200
committerMårten Kongstad <amhk@google.com>Thu May 02 14:30:56 2024 +0200
tree7ac3bf5630905d7daa897ac9747a7df56c877ea8
parentcd93aeb947fe79c191ef2f7dde1853571c40c236 [diff]
check-flagged-apis.sh: use correct path to generated API signature files

The path to the generated API signature files used with --api-signature
in the check-flagged-apis.sh script are different based on the lunch
target used: sometimes it's under $ANDROID_PRODUCT_OUT, other times
under out/target/product/mainline_x86.

Teach check-flagged-apis.sh to dynamically find the correct path by
querying ninja.

Bug: 334870672
Test: croot && build/tools/check-flagged-apis/check-flagged-apis.sh
Change-Id: I1b0b41ef3ad1bc7113a3b31323d81251e7e65933
1 file changed
tree: 7ac3bf5630905d7daa897ac9747a7df56c877ea8
  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. METADATA
  20. navbar.md
  21. OWNERS
  22. PREUPLOAD.cfg
  23. rbesetup.sh
  24. README.md
  25. shell_utils.sh
  26. tapasHelp.sh
  27. 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.