|tagger||The Android Open Source Project <email@example.com>||Tue Dec 11 15:39:57 2018 -0800|
Android 9.0.0 release 22 -----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQRDQNE1cO+UXoOBCWTorT+BmrEOeAUCXBBKzQAKCRDorT+BmrEO eO03AJ4pWnwMXsk+X9hTN8+CLyVyd1ffsQCeL/g5N78vOkgDxefSNZxlRsh8JBU= =0Ew7 -----END PGP SIGNATURE-----
|author||android-build-team Robot <firstname.lastname@example.org>||Mon Nov 26 18:38:17 2018 +0000|
|committer||android-build-team Robot <email@example.com>||Mon Nov 26 18:38:18 2018 +0000|
Version bump to PQ1A.181205.006.A1 Change-Id: I7da1787eec128cf5d7dce811ae57cd7182a35e4f
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.