commit | 308d02fd62dd997d4e83c0efe71fd4f8a6e0c975 | [log] [tgz] |
---|---|---|
author | Justin Yun <justinyun@google.com> | Tue Mar 21 14:26:02 2023 +0900 |
committer | Justin Yun <justinyun@google.com> | Tue Apr 25 08:14:58 2023 +0000 |
tree | f90f2ffe518210ab6a92c34aceae1dc647dd64a6 | |
parent | 60588af876e124a2f0ae6d5379bdfa029eac950a [diff] |
Enforce product interface by default We have both with/without product interface enforced targets. Because of this, unbundled apps in the product partition must consider bundled cases and has to add `jni_uses_platform_apis: true` to use jni libraries. As targets with PRODUCT_SHIPPING_API_LEVEL > 29 must enforce the product interfaces, if PRODUCT_SHIPPING_API_LEVEL is not defined, enforce the product stable interface by default. Bug: 273386586 Test: TH Change-Id: I5874bf0ae8477fab7b1097ad24c9cc0d95543eb1
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.