commit | 41cada8d4e9b91386d9b691c4ae485425ef6a62e | [log] [tgz] |
---|---|---|
author | Priyanka Advani (xWF) <padvani@google.com> | Wed Mar 26 17:35:36 2025 -0700 |
committer | Gerrit Code Review <noreply-gerritcodereview@google.com> | Wed Mar 26 17:35:40 2025 -0700 |
tree | 0c07ddbf7e4f41b0dd6ba2a3408195453e98f11f | |
parent | 83e2bca7cb4a87cc1afd214df9641c60fb80c4e3 [diff] |
Revert "Don't attempt to copy test files for soong modules" Revert submission 3540409-install_test_files_with_soong Reason for revert: Droidmonitor created revert due to b/406602299. Will be verifying through ABTD before submission. Reverted changes: /q/submissionid:3540409-install_test_files_with_soong Change-Id: Ieb3cf82820b1ee2fb2f224c56bda1b7dc77fdbd3
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.