| commit | 68684bea792983971ed3c36052a416e9af1701bf | [log] [tgz] |
|---|---|---|
| author | Spandan Das <spandandas@google.com> | Tue Nov 02 03:54:05 2021 +0000 |
| committer | Spandan Das <spandandas@google.com> | Thu Jan 06 18:47:57 2022 +0000 |
| tree | 35afd04cde34417fb368b6004e268c6408ec285e | |
| parent | 3293a959ad29ff4597c1163742a3d62ed73d8370 [diff] |
Move manifest generation logic into static_java_library.mk Previously a manifest file would be generated for static_java_library.mk and package_internal.mk. For pacakge_internal.mk, this would cause cryptic errors like b/188612215#2 With this CL, a manifest file would only be generated for java_library with need_compile_res == true. The advantages are 1. No redundant generation for java_library with need_compile_res == false (i.e. modules that do not require aapt2) 2. Force devs to provide manifest for android_app, and not silently generating one for them Bug: 188652897 Test: TH Test: m nothing in tv-dev, car-dev Change-Id: I69a23e373f1b4ac1569ae5b1d36067bfc0dadc05
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.