| commit | 91af68b1e10daa8ca1cf2433430eafe5c079a36f | [log] [tgz] |
|---|---|---|
| author | Bob Badour <bbadour@google.com> | Mon Jan 31 13:11:11 2022 -0800 |
| committer | Bob Badour <bbadour@google.com> | Mon Jan 31 14:14:27 2022 -0800 |
| tree | f03ef235cb135f2b7080162a96861cd1799c7adc | |
| parent | afe22b9a74172a021cf97b2ba9e531087896c32c [diff] |
Fix copy+paste error.
The tool under test is dumpresolutions not listshare.
Test: m dumpresolutions; out/soong/host/linux-x85/dumpresolutions ...
where ... is the path to the .meta_lic file for the system image. In my
case if
$ export PRODUCT=$(realpath $ANDROID_PRODUCT_OUT --relative-to=$PWD)
... can be expressed as:
${PRODUCT}/gen/META/lic_intermediates/${PRODUCT}/system.img.meta_lic
Change-Id: Id3d6e701ebd3dab03f407116d85a5e2aab8c5c59
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.