| commit | 62d0a739bbce94f3f3721e036ca9b2df94e18ba1 | [log] [tgz] |
|---|---|---|
| author | Devin Moore <devinmoore@google.com> | Thu Oct 13 16:50:50 2022 +0000 |
| committer | Devin Moore <devinmoore@google.com> | Mon Oct 17 19:48:46 2022 +0000 |
| tree | 37b816d1ba3447c259f81c94081b254acfa95c8f | |
| parent | 1c5f813bf0ece71587acf5d8f71f14194046d7e8 [diff] |
Restrict the framework manifest check against frozen files This only needs to be done for GSI targets that need to remain compatible with previously frozen manifests so they continue to work for older upgrading devices. Test: lunch aosp_cf_x86_64_phone && m Test: lunch aosp_arm64 && m Test: both tests with and without android.hidl.manager served on device Bug: 218588089 Change-Id: I34862b08cd4ba4c554b5fe9db0eeacba60a0c33a
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.