| commit | 523696e964a07ad2238871081b88a39570f74dfd | [log] [tgz] |
|---|---|---|
| author | Ronald Braunstein <rbraunstein@google.com> | Tue Apr 30 10:54:48 2024 -0700 |
| committer | Ronald Braunstein <rbraunstein@google.com> | Fri May 31 08:23:08 2024 -0700 |
| tree | 1a9e26e4d9c9573389bc9737dd4d5243c4da9371 | |
| parent | 6d52c945d50783333a82e7311e876f54bcc7c1a6 [diff] |
Add soong installed files to general-tests.zip The module `test_module_config` will be installing symlinks in the testcases directory pointing back to the `base` test for .apk files. This saves a gigs of space on disk and in suite zip files. However, the .mk files were using LOCAL_COMPATIBILITY_SUPPORT_FILE to do two things: 1) copy the file from intermediates to testcases 2) package the testcases files in zips. Because the test_module_config rule is taking care of 1), we need a new variable to do just 2) Test: m general-tests device-tests Change-Id: Icdad4401cde27d8edd5e13e486b96c62817a4bbb
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.