| commit | 1a9d81a06b7c794b297c13bc2d57f38c5f522b09 | [log] [tgz] |
|---|---|---|
| author | Anton Hansson <[email protected]> | Wed Nov 25 18:15:33 2020 +0000 |
| committer | Anton Hansson <[email protected]> | Wed Dec 09 17:16:52 2020 +0000 |
| tree | d142b2b033597151847d5edc1067f2e6cfcfc29b | |
| parent | 7eb5ddcb24d03a74dffa936c53487080690dfc39 [diff] |
Add bootclasspath config to its own makefile This is part of adding some devices/products suitable for unbundled builds. An unbundled product does not need all the PRODUCT_PACKAGES etc present in the normal hierarchy of products, but does need to know which jars are on the bootclasspath. Therefore, factor out the bootclasspath config from base_system.mk and put it in its own makefile where it can be inherited by these unbundled products. Bug: 172256440 Test: diff presubmit artifacts (noop) Merged-In: Id3f91e387bba2e0525b4010f22fe380d1d8be537 Change-Id: Id3f91e387bba2e0525b4010f22fe380d1d8be537
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.