| commit | 44f762a7661adf068d56d041537597b541b02c9e | [log] [tgz] |
|---|---|---|
| author | Ulya Trafimovich <skvadrik@google.com> | Tue Sep 21 12:57:59 2021 +0100 |
| committer | Ulya Trafimovich <skvadrik@google.com> | Thu Sep 23 12:10:04 2021 +0100 |
| tree | 773265fc31b4f4e52332681688c32f3e79fc69d4 | |
| parent | 4528968faf0715fc0f3d7fd9b1767e11177229d6 [diff] |
Move copy rule for system server jars from dexpreopt_gen to makefiles. This is necessary in order to expose the copy rule to Ninja. Otherwise Ninja has a build rule that depends on the copied jar (namely, dexpreopt commands for all subsequent system server jars that have the current one in class loader context), but no rule that creates it, so Ninja fails with a "no rule to make ..." error. The change only affects system server ed in Android.mk Previously the problem existed, but was hidden by the fact that the only system server jar defined in Android.mk was the last one on the list, so no other jar depended on it. Now that updatable apex jars are also dexpreopted (https://r.android.com/1828115) the problem was uncovered. Also the patch removes obsolete logic that disable dexpreopt for PRODUCT_APEX_SYSTEM_SERVER_JARS; these jars are now preopted (but they are all defined in Android.bp anyway, so no functional change here). Bug: 200297762 Test: lunch bertha_x86_64-userdebug && m Change-Id: I67c6d69f45ca3495f62994b5329f9e424dda4e65
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.