commit | adc94a151a126b8f30f19bd277debc1ee5b3f6da | [log] [tgz] |
---|---|---|
author | Victor Hsieh <victorhsieh@google.com> | Tue Sep 20 11:46:09 2022 -0700 |
committer | Victor Hsieh <victorhsieh@google.com> | Tue Sep 20 14:53:51 2022 -0700 |
tree | f16094d16f4a90e5ec80d8d6761671027925722e | |
parent | cfb5fb522719373f0739fdbaf9d22f69df477b10 [diff] |
Remove fs-verity build manifest for vendor/odm/product The build manifest APKs are recently added because we thought it's nicer for ART to support beyond system_ext for potential partner customizations. Jiyong pointed out that having system server JARs outside of system and system_ext may be a Treble violation. As a result, delete some of those files. Bug: 246000387 Bug: 245957815 Test: m; no longer seeing the files under out/ Change-Id: I4c5b118bd2277b5f3265ac4d3c2343cf929822c5
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.