commit | e06e4c5037272c95942334300a1f7b8cdc31b59d | [log] [tgz] |
---|---|---|
author | Jihoon Kang <jihoonkang@google.com> | Tue Sep 19 19:12:48 2023 +0000 |
committer | Jihoon Kang <jihoonkang@google.com> | Wed Sep 20 19:53:04 2023 +0000 |
tree | d25419e201a7aae48ae27b52b4426a7c5085ff1a | |
parent | b00035955c6ce31bd2a542303358674bacb0b291 [diff] |
Add PRODUCT_NEXT_RELEASE_HID_FLAGGED_API for sdk targets PRODUCT_NEXT_RELEASE_HIDE_FLAGGED_API added to the sdk targets will be used to determine whether to exclude flagged apis for next release or not. Test: m TARGET_PRODUCT=sdk nothing Bug: 299570421 Change-Id: I00cb84341a05e296a0c747d4921ed5fe445eabe6
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.