| commit | d4e4b64eebc5a09a22f85deda25aa21e447d1ff0 | [log] [tgz] |
|---|---|---|
| author | Luca Farsi <lucafarsi@google.com> | Tue Sep 10 16:37:51 2024 -0700 |
| committer | Luca Farsi <lucafarsi@google.com> | Tue Sep 10 16:37:51 2024 -0700 |
| tree | 026edfd2db34cc7ade5a73231375c2c94f1790c5 | |
| parent | 7c112657244506c784b4ea4bf8b2d70ae7ef2d9f [diff] |
Refactor package_outputs Refactor package_outputs in the TestOptimizer so it just returns a list of soong_zip commands to be run by build_test_suites. Since we already have a tested implementation for running subprocesses in build_test_suites.py there's no reason to reimplement it in optimized_targets.py. Because any packaging will ultimately use soong_zip to package its final outputs change the code to just do whatever prep it needs to and return a list of soong_zip commands. This way the code is simpler to test without requiring subprocesses and no reimplementation of subprocess running code is necessary. Test: atest build_test_suites_test; atest optimized_targets_test Bug: 358215235 Change-Id: I3025aefeeb7186f537266a72d8422211ca9835ba
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.