commit | 224e103308a80fa6440bddb3798ccafdffb14bd7 | [log] [tgz] |
---|---|---|
author | nelsonli <nelsonli@google.com> | Fri Dec 14 17:26:57 2018 +0800 |
committer | nelsonli <nelsonli@google.com> | Thu Mar 07 14:08:35 2019 +0800 |
tree | 51508ec877e84d09a81988b6adff6778825c946f | |
parent | e34ff5ca5d1d5d9f138b2a3e59962d2b65b97c09 [diff] |
Build System: Solve dependency problem for test 1. A test can add a runtime dependent test module by just setting LOCAL_REQUIRED_MODULES or LOCAL_TARGET_REQUIRED_MODULES. Then the dependent test module will be copied to testcase folder. 2. Do not install to $(TARGET_OUT_DATA) for testcase BUG: 117224272 Test: 1. (a) vi cts/tests/tests/text/Android.mk (b) add LOCAL_REQUIRED_MODULES := CtsPrintTestCases (c) m -j CtsTextTestCases (d) Then, CtsPrintTestCases should also be built to testcase folder like below. ./target/product/generic_arm64/testcases/CtsPrintTestCases Change-Id: I24ea3783486c54a05cfa9d3d0375b977afc230f8
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.