| commit | 82eb7ac553d00b5c43cad32175c8a8ceb7e9a861 | [log] [tgz] |
|---|---|---|
| author | Spandan Das <spandandas@google.com> | Wed Feb 12 22:20:41 2025 +0000 |
| committer | Spandan Das <spandandas@google.com> | Wed Feb 12 22:24:08 2025 +0000 |
| tree | 7930ea0ef55424b92b603e4276656a172965f071 | |
| parent | b664c8eb244c4f5c415e1db7062ab344ab4fbc4c [diff] |
Declare inputs of $PRODUCT_OUT/system_server.zip https://r.android.com/3062109 switched system_server.zip generation to read the files from an intermediates directory assembled by a soong singleton, and not from $PRODUCT_OUT. However, it did not update the inputs. This silently relied on the fact that depending on the system server jars in PRODUCT_OUT would assemble the jar in the soong intermediates directory This CL makes the input explicit. Bug: 396162261 Test: m $PRODUCT_OUT/system_server.zip Test: aninja -t query $PRODUCT_OUT/system_server.zip (verified that out/soong/system_server_dexjars/services.jar is listed in inputs) Change-Id: I087597e26562250c9870cf636cd457ad3a1394c8
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.