commit | 2ff485ac21fdedae40817c0a2c7be3fd10b86b05 | [log] [tgz] |
---|---|---|
author | Neil Fuller <nfuller@google.com> | Mon Jun 10 04:07:54 2019 -0700 |
committer | android-build-merger <android-build-merger@google.com> | Mon Jun 10 04:07:54 2019 -0700 |
tree | c65239edd6bf26d5dff3986467c6c40f9a685643 | |
parent | ff2dc3f2fcfc5ba228ec1dccb2ceea0106121c84 [diff] | |
parent | 106a3210d869e137d9b9fc18341f05afc5147020 [diff] |
[automerger skipped] Merge "Add a host simulation of the tzdata module" am: 69324709f8 am: 106a3210d8 -s ours am skip reason: change_id I43dadb150e359bbcb9da61e0187286ac6d38f7c2 with SHA1 8236702567 is in history Change-Id: I377b5b60f6583eb37d454a0de7eebb0fcc632840
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.