| commit | d4a51e5cbfe5e937628d290c4de5857360e9b108 | [log] [tgz] |
|---|---|---|
| author | Jihoon Kang <jihoonkang@google.com> | Wed Nov 06 00:28:41 2024 +0000 |
| committer | Jihoon Kang <jihoonkang@google.com> | Wed Nov 06 00:28:41 2024 +0000 |
| tree | 48442e4e36cd2122b8a5d53626316b433ec1f854 | |
| parent | dfb457c873034dd5bdfbc43df9ff84e9441a3157 [diff] |
Specify product_specific property in adb_keys The module installs the output file in product partition. This change allows Soong to recognize it. Test: m soong_generated_product_filesystem_test Bug: 376515714 Change-Id: Idce4ac4974ea0331caf1f13f42e0dd57e0ec73d8
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.