commit | f90b734c0c6fb8365c8f707ec11b6128f4e6e0ba | [log] [tgz] |
---|---|---|
author | yangbill <yangbill@google.com> | Tue Aug 28 20:40:42 2018 +0800 |
committer | Bill Yang <yangbill@google.com> | Thu Aug 30 05:06:32 2018 +0000 |
tree | 813947d9865de8e01af3dd0becb0833d7822c606 | |
parent | d7eaae0f09ecd03218251b6049494682ea4e5168 [diff] |
ATest: Change module_name from list to single string. ATest's original module_name is designed as a single string. The different type maybe cause some problem when loading module_name data. Due to it expected it as a list but actually it will be a single string after mod-info obj handling this data. Bug: 113317515 Test: atest aapt2_tests atest hello_world_test atest BluetoothInstrumentationTests atest packages/apps/Bluetooth/tests/unit/Android.mk atest RunBluetoothRoboTests atest com.android.bluetooth atest libcore/luni/src/test/java/libcore/javax/net/ssl/SSLSocketTest.java Multiple tests found: 0: libjavacore-unit-tests 1: jsr166-tests 2: core-ojtests-public ... atest SSLSocketTest # Brings up 2 prompts, one for which file then one for which module make -j bit bit Settings bit hello_world_test bit BluetoothInstrumentationTests bit RunBluetoothRoboTests (Could not find module, but the same situation before applying this patch) Change-Id: I46a14c675eabd7cebd82562954380a9a769e80b5
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.