commit | 85f5c34e0a1dd0c382f3fe33734e3626b65ee4d8 | [log] [tgz] |
---|---|---|
author | Nelson Li <nelsonli@google.com> | Mon Mar 25 08:39:08 2024 +0000 |
committer | Nelson Li <nelsonli@google.com> | Tue Apr 02 02:43:48 2024 +0000 |
tree | c65b5894f207678f6d4351333ab4a214ca1c0b4a | |
parent | eb59dd9cbd4519a5aa7405cb605220de9763f557 [diff] |
Move berberis tests to build/core/tasks Move the executes `berberis_host_tests_result` and `berberis_run_host_tests` to `build/core/tasks`, as Soong might currently have difficulty supporting this part. Set the OWNER of berberis_test.mk Bug: 321643544 Test: 1. lunch sdk_phone64_x86_64_riscv64-trunk_staging-eng 2. m berberis_all 3. m berberis_host_tests_result 4. m berberis_run_host_tests Change-Id: I44a03e9eae9ee6a3c82a6d2e6de3a03b2c7d81da
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.