| commit | 4416313943bea029dee87c56855ca8479b057e41 | [log] [tgz] |
|---|---|---|
| author | Jeff Sharkey <jsharkey@google.com> | Mon Nov 13 14:02:13 2023 -0700 |
| committer | Makoto Onuki <omakoto@google.com> | Thu Feb 08 11:33:45 2024 -0800 |
| tree | 523ae307422c00d93b3d3cedc8fe78ef01d9b2a4 | |
| parent | e406793f57ab05aa558db542127457376d4cbfcc [diff] |
Update XML template to reflect null device. Ravenwood doesn't need a device, so add a "null" filter so that atest doesn't hang waiting for one. Bug: 292141694 Test: atest-dev CtsOsTestCasesRavenwood CtsOsTestCases Merged-in: I10ceeae92c7622ea44ecbc315e23babe8b36516a Change-Id: I10ceeae92c7622ea44ecbc315e23babe8b36516a
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.