commit | 439b829b42e557f072436613ba987b7928680433 | [log] [tgz] |
---|---|---|
author | Jiyong Park <jiyong@google.com> | Tue Dec 03 12:54:35 2019 +0900 |
committer | Jiyong Park <jiyong@google.com> | Tue Dec 17 21:16:34 2019 +0900 |
tree | 8abd6c82fec33f4467644a78919d5640e3e83a49 | |
parent | 0d7bd6be90e371b76884f01524437223fdcd7a23 [diff] |
Find the jar libraries in APEX from the correct path JAR libraries in the ART and conscrypt APEXes are no longer built for the platform. Therefore, the path out/target/common/<name>_intermediates does not exist. Instead use the path out/target/common/<libname>.<apexname>_intermediates paths for those APEX-only jars. Bug: 128708192 Bug: 133140750 Test: m Change-Id: I5fb725403ac22198e5ce6d77ca97c5f3392fabfd
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.