| commit | e234e6c32001c7a2e6a1de8bba1441fe55616d6d | [log] [tgz] |
|---|---|---|
| author | Pierre-Clément Tosi <ptosi@google.com> | Wed Oct 06 08:33:42 2021 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Oct 06 08:33:42 2021 +0000 |
| tree | fa6cbcbd0612565b79223783be43ac850a6d51df | |
| parent | d423a17b9b64cb538c3f3f707418f8885cf24870 [diff] | |
| parent | 0ce85eaf51c67d1a2a7e71cf6eb0df992772c9eb [diff] |
Merge changes from topic "default-pvmfw-image" am: b3be181687 am: ab1d0dc36e am: 6308e21f92 am: 0ce85eaf51 Original change: https://android-review.googlesource.com/c/platform/build/+/1832464 Change-Id: Ia0e2e41a82c4ba212e815df9d9507e98ce419f00
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.