| commit | 7160b06db92cb34115191eb7e5f54fd8482084af | [log] [tgz] |
|---|---|---|
| author | Simran Basi <sbasi@google.com> | Mon Jan 08 12:25:18 2018 -0800 |
| committer | Simran Basi <sbasi@google.com> | Mon Jan 08 13:03:07 2018 -0800 |
| tree | ea2b6d0faa95e072a42028e12cc8d893a6fd5212 | |
| parent | e3692095a1f201071fc50f5940094388bac81846 [diff] |
base_rules.mk: Don't use is_native for MULTILIB modules. Currently we determine if a test artifact has multiple build outputs by checking if it is NATIVE_TEST, NATIVE_BENCHMARK, or LOCAL_MULTILIB and declare the module is_native. This is technically not true therefore let's use a different variable to determine if we need multiple architecture directories. Bug: 71554249 Test: make sl4a -j ; Results in an autogenerated empty configuration file. Change-Id: I17c8f3ef7e1cd502b57e25c71688f12a35a9787d
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.