| commit | 26c0d8a4e7fed6dbb8f67b4970c43282b31ae62f | [log] [tgz] |
|---|---|---|
| author | Luca Farsi <lucafarsi@google.com> | Fri Nov 22 00:09:47 2024 +0000 |
| committer | Julien Desprez <jdesprez@google.com> | Sat Dec 07 02:46:51 2024 +0000 |
| tree | 4039452f48496dfe2aac2509695e3ac16739d231 | |
| parent | 62035d9c960049e188f1d593180f25e0bb8c9d8e [diff] |
Enable real test discovery in build_test_suites Enable test discovery to actually affect build targets in build_test_suites.py (only when the flags are enabled. On failure of test discovery or if the flags are off instead fall back to the previous optimizations. Change-Id: I6937dd0c5096884095d0770bc53b6399233cefc2 Test: atest build_test_suites_test Bug: 378926009
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.