| commit | a631430c4678b58c131ffbb60e8639d52bf87f7b | [log] [tgz] |
|---|---|---|
| author | Martin Stjernholm <mast@google.com> | Fri May 10 11:23:43 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Fri May 10 11:23:43 2019 -0700 |
| tree | a39019b7c38eb14829b6c8d8479310b9fae49a82 | |
| parent | 6ae401e8d3f1bdf792a8ebc2ae0777119f26835f [diff] | |
| parent | e954e3e47da8ff2228de358e70f8bbc7bb0dd00c [diff] |
[automerger skipped] Add the library absence check as a kati stage check. am: e954e3e47d -s ours am skip reason: change_id I7a93cc0ac4480404a3d56c75eb43ae499e8a3a05 with SHA1 b0382f0319 is in history Change-Id: I906e1e104d5d7cb06d0a975945c17e22a40debf3
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.