commit | e219f0068a0c6827447a4377dfd2a4ad72efcd5a | [log] [tgz] |
---|---|---|
author | Jiyong Park <jiyong@google.com> | Fri Dec 16 14:30:03 2022 +0900 |
committer | Jiyong Park <jiyong@google.com> | Fri Dec 16 14:30:03 2022 +0900 |
tree | a222aa70a070feffaf3f54404753e9475169213f | |
parent | 2dcc38701b38bddf62e4dfc25d9e063ba5e5f203 [diff] |
Place unstripped pvmfw image to the symbols directory Bug: 245896220 Test: examine the symbols.zip file on aosp_cheetah Change-Id: I8730baa64e6ff16fcdf765dc8878771d2ec16be8
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.