| commit | 24f62069d00758eb7b37b9dd61b4f01e6621665f | [log] [tgz] |
|---|---|---|
| author | Paul Duffin <paulduffin@google.com> | Fri Apr 02 10:59:32 2021 +0100 |
| committer | Paul Duffin <paulduffin@google.com> | Tue Apr 06 11:53:08 2021 +0100 |
| tree | 71a1ac9663fb3ba76d0c611ccb81179a46c0d621 | |
| parent | bebc8a35ef49335f59614b29937e0ab36cf248ed [diff] |
Remove use of REMOVE_ATB_FROM_BCP This change cleans up after the work to remove the android.test.base classes from the bootclasspath. That work allowed the presence of android.test.base in the bootclasspath to be configured at build time to allow the changes to be tested without affecting the standard Android builds and avoiding having to repeatedly reapply/revert the changes that excluded android.test.base from the bootclasspath. That change has been applied and stuck and no builds change the default by setting REMOVE_ATB_FROM_BCP=false so we no longer need to support that capability. This change removes the build time switch to add framework-atb-backward-compatibility to the bootclasspath and another change in the same topic merges those classes into the framework-minus-apex module. So, while a module has been removed from the bootclasspath the classes available on it have not changed. Bug: 184331423 Test: m nothing Change-Id: I9dadaf8b0c2684bf1983b353bb2acf4f42655e1a
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.