| commit | 8531ca4d1afcdd733276c5c6b5593029bbd6d9a2 | [log] [tgz] |
|---|---|---|
| author | Paul Duffin <paulduffin@google.com> | Thu Oct 29 12:56:09 2020 +0000 |
| committer | Jackeagle <jackeagle102@gmail.com> | Sat Dec 12 07:25:55 2020 +0100 |
| tree | e8490a97a2ebdc3e26d0a9cba8b2f966684086b0 | |
| parent | 31a2f8814bd20714ccecb20cb0f92c46913bdc71 [diff] |
Switch boot jars package check to using dex jars The switch to use dex jars instead of class jars means that a boot jar that is defined by a dex_import module will now be checked against the package_allowed_list.txt so it is possible that it will detect previously unreported problems. Test: m check-boot-jars - for failing and passing cases Bug: 171479578 Bug: 125517186 Change-Id: Ie614898dade0fb43c9418d7afb9138169db6f097
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.