| commit | 43c247e181ca4f07992126f351355f1beb8c2a18 | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Wed May 02 12:52:43 2018 -0700 |
| committer | Colin Cross <ccross@android.com> | Wed May 02 13:11:08 2018 -0700 |
| tree | a360e792c3d0a0daed97de629f5d02e0b5994971 | |
| parent | fc8e281bc3ce10933343595f38a586844fd9ab66 [diff] |
Regenerate R.java files from LOCAL_STATIC_ANDROID_LIBRARIES If a static android library lib1 has LOCAL_STATIC_ANDROID_LIBRARIES lib2, then the R.class files for packages in lib2 will be merged into the jar for lib1. If an app has lib1 in its LOCAL_STATIC_ANDROID_LIBRARIES it will get the R.class files from lib2 through lib1, instead of regenerating the R.java files with numbering that matches the resource table of the app. This was worked around for support libraries by keeping a fix_dependencies.mk that added transitive static support libraries to the direct static dependencies of apps. Instead, propagate the packages that aapt2 generated R.java files for up as --extra-packages arguments to the next aapt2 invocation, which will force aapt2 to regenerate the R.java files for those packages. Bug: 78300023 Test: m checkbuild Change-Id: I7375e13241b4c4f2933032409fb7935abe133bfc
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.