| commit | 55a8f02ea87366705c954860a543ffec9c7b52c8 | [log] [tgz] |
|---|---|---|
| author | Anton Hansson <hansson@google.com> | Thu May 12 08:45:29 2022 +0000 |
| committer | Anton Hansson <hansson@google.com> | Thu May 12 12:28:49 2022 +0000 |
| tree | 0b73ffaa3382dc32a008783dc10e2698ffe69e7c | |
| parent | 8ccac5198d118d9916ed10125929afa34d9987f0 [diff] |
Remove unused dependencies from sdk goals The SDK no longer includes system images, so no longer needs to depend on targets that are only relevant for the system images. Remove all the explicit dependencies that end up depending on "everything" but are not included in the sdk zip. Two positive side-effects: - fewer unused things get built (now ~32k targets, down from ~108k) - apexes no longer get built, eliminating the risk of mismatch between module sdk prebuilts and source-built AOSP apexes. There are some potential risks with this CL: - because we no longer forcefully rebuild everything, if there are bugs in dependencies of exising files in the SDK, incremental builds may not rebuild them. - some files that get built into the SDK may be being built as a side-effect of other files included in the SDK, so removing one file may cause another to not get built. The solution to that is to add the file not getting built to ALL_SDK_FILES. Bug: 205008975 Test: m sdk sdk_repo dist && diff sdk.zip before/after (identical) Change-Id: I97284864f66aa88556fbe16864f45b04be97634e
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.