| commit | d94bb431aaff8468c07757b65243e6c8cc917abd | [log] [tgz] |
|---|---|---|
| author | Trevor Radcliffe <tradical@google.com> | Tue Mar 22 19:04:03 2022 +0000 |
| committer | Trevor Radcliffe <tradical@google.com> | Tue Mar 22 19:04:03 2022 +0000 |
| tree | c872b669edb390545a7bafac2716ec0a12ff7db5 | |
| parent | 2089403223746ffde8050e68bdc30d40634b981a [diff] |
Add DeviceProduct product varible to Soong For some modules, it is necessary to access the product name from Soong. In particular, the use case we have identified is that the product name needs to be appended to the artifact name in the dist copy. Bug: 224561567 Test: Unit Tests and build relevant target/modules Change-Id: Iaa0bfee8ef0d1201d8af02f7fc9e6ef081175da7
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.