Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / 49f08d9328f83d32540038a42b5c14d9413af430
commit49f08d9328f83d32540038a42b5c14d9413af430[log] [tgz]
authorJihoon Kang <jihoonkang@google.com>Thu Feb 22 20:04:44 2024 +0000
committerJihoon Kang <jihoonkang@google.com>Thu Feb 22 20:08:53 2024 +0000
tree2120ca1acbaa99f17c3c0feb06729d7626aac77b
parentc974a2786fa8d47bfa8eb5a2c251900232115c9d [diff]
Introduce the product variable PRODUCT_EXPORT_RUNTIME_APIS

PRODUCT_EXPORT_RUNTIME_APIS is a product variable that inherits the
behavior of the build flag RELEASE_EXPORT_RUNTIME_APIS, which is being
removed. This will be utilized in the product `sdk_with_runtime_apis`,
which will be introduced in a future change.

Test: m nothing --no-skip-soong-tests
Bug: 326312949
Change-Id: I4966b7bfc7423db049acfcede67233352ba8341b
2 files changed
tree: 2120ca1acbaa99f17c3c0feb06729d7626aac77b
  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.