| commit | d9682377fe9097e97b88aa9b67e6b1cce7226771 | [log] [tgz] |
|---|---|---|
| author | Roman Kiryanov <rkir@google.com> | Wed Nov 09 12:24:16 2022 -0800 |
| committer | Roman Kiryanov <rkir@google.com> | Wed Nov 09 12:24:16 2022 -0800 |
| tree | c79d036b466c56b2c6dcee6046d630302e7dc2ee | |
| parent | 2a273f50d47f7686905beee2c3e223d7c2888cfd [diff] |
Add a ramdisk stub for targets that referred to goldfish's arm32.mk there is a check that requires the ramdisk to be nonempty. Bug: 250696437 Test: presubmit Change-Id: If3918ec1eb0e6263ed845e48c7415755c0cfc832 Signed-off-by: Roman Kiryanov <rkir@google.com>
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.