commit | 7bf03bf68e63c764b1fd04337524a8416b8dc190 | [log] [tgz] |
---|---|---|
author | Colin Cross <ccross@android.com> | Thu Nov 16 15:39:13 2023 -0800 |
committer | Colin Cross <ccross@android.com> | Wed Nov 29 10:18:52 2023 -0800 |
tree | c14f19de9f08d10cbaaefa398fdd63eddd148b2f | |
parent | 4ea5e85143c7bfce14e6ac78fd34fa91cbb2552e [diff] |
Fix test data to use my_test_data_file_pairs The format of LOCAL_TEST_DATA when provided by Soong can included a third colon-separated field with an extra relative path that is not being handled when assigning to ALL_MODULES.$(my_register_name).TEST_DATA. Use my_test_data_file_pairs instead, which has already been transformed to a src:dest pair. Bug: 311428265 Test: examine module-info.json Change-Id: I3a089cc24ea1492f1f7cf891c73ee7b43f273bb3
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.