| commit | 41c3ad1f8bfb3e1f5fece6692d0e4bb2a2e8c4f4 | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Thu May 14 12:49:15 2020 -0700 |
| committer | Colin Cross <ccross@android.com> | Fri May 15 10:09:57 2020 -0700 |
| tree | bc5435817a9394fb2106def1c0e2105a89fcd291 | |
| parent | 4d8e9cc8475a20e6f577fa95168584aebfbfc5ad [diff] |
Don't check link type of Soong app JNI libraries Link type checking is already done within Soong, and SOONG_SDK_VARIANT_MODULES is not complete yet while parsing Soong modules, skip JNI link type checking for Soong apps. Bug: 156225490 Test: m checkbuild Change-Id: I2f6824b180ccdd62c26497bdca527540ca22f0d7 Merged-In: I2f6824b180ccdd62c26497bdca527540ca22f0d7 (cherry picked from commit 1c8d81e5d93274cd36bdb6708817084dabe47bc8)
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.