| commit | 8ea6742d053bb674c67a4b5c35e621a76462aa72 | [log] [tgz] |
|---|---|---|
| author | Luca Farsi <lucafarsi@google.com> | Tue Sep 17 15:48:11 2024 -0700 |
| committer | Luca Farsi <lucafarsi@google.com> | Thu Sep 19 11:01:06 2024 -0700 |
| tree | 236ef67bbe8a53eefa8eeb5d5308c54ceb032796 | |
| parent | 75501177a56a3a3342a58cf573961f6d83b27cf9 [diff] |
Fix packaging outputs commands There were a few issues with the output packaging process that were found during testing of the general-tests optimization. First and foremost is that the packaging commands were trying to be created before the build ran, when the outputs don't exist. I've changed the logic to just collect the methods themselves which will then be run during build plan execution after the build has completed. A few other smaller issues include fixing the path to the soong_zip binary, incorrect execution of the soong dumpvars command, and not building the shared libs zip. Test: atest build_test_suites_test; atest optimized_targets_test Bug: 358215235 Change-Id: I8a3f54738f8bb5d871aadf7423844076c38b54a6
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.