| commit | 18f6e105e98836a09cf3465662927035bc85e037 | [log] [tgz] |
|---|---|---|
| author | Luca Farsi <lucafarsi@google.com> | Thu Jan 09 10:18:28 2025 -0800 |
| committer | Luca Farsi <lucafarsi@google.com> | Thu Jan 09 20:53:04 2025 -0800 |
| tree | fe0b083c3979d38fa7f0c69e6f92db06285e82b0 | |
| parent | b1d766b951bd5061152f2485551656bbb9a9febd [diff] |
Add option for test discovery info mode Add a command line option to enable test discovery info mode, where enabling it will cause test discovery to run and report results but not actually affect the build. This is useful for rolling out to new targets without immediately enabling test discovery mode. Test: atest build_test_suites_test Bug: 388833029 Change-Id: I8baf73e6353e4c3d7d6836c4f9823341a7f8b5dd
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.