| commit | e472adf4d56ed6aab06ab69573246b5f9cffe8cd | [log] [tgz] |
|---|---|---|
| author | Dennis Shen <dzshen@google.com> | Wed Oct 02 19:02:05 2024 +0000 |
| committer | Dennis Shen <dzshen@google.com> | Wed Oct 02 21:28:42 2024 +0000 |
| tree | af6abf277bd2d5aa1d76f129cc6a3697ee89e793 | |
| parent | d29187877e60b501122c29873d5e61f118e9c4cf [diff] |
add the test config lib to a target that is used in platform build There are tests that uses aconfig flag libs that are not used by actual platform build. So querying these flags will fail in new storage as they are not present in storage files. Short term fix is to add them to platform build depdenency. Change-Id: I8b485ad65e2fa91258165c3a15c5d509b30d4018
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.