commit | e9525900e5b49799cf1f79ece8d48c4eebcd7120 | [log] [tgz] |
---|---|---|
author | Justin Yun <justinyun@google.com> | Tue Sep 12 16:13:37 2023 +0900 |
committer | Justin Yun <justinyun@google.com> | Wed Sep 13 13:07:34 2023 +0900 |
tree | 37b23acbc0fd334b988ce50be67c1565e6122934 | |
parent | f3c3f40c3bd386867ef140db4b7f50190bd85930 [diff] |
Do not freeze VNDK in trunk stable VNDK will be frozen only if the VNDK version is less than or equal to 34. Otherwize do not freeze the VNDK libraries. Bug: 297542516 Bug: 299867815 Test: lunch cf_x86_64_phone-next-userdebug; m Change-Id: Icdd288f65c5f7bdb5b4899c8e96820c2a147a011
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.