| commit | 6ae401e8d3f1bdf792a8ebc2ae0777119f26835f | [log] [tgz] |
|---|---|---|
| author | Martin Stjernholm <mast@google.com> | Fri May 10 11:23:11 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Fri May 10 11:23:11 2019 -0700 |
| tree | a39019b7c38eb14829b6c8d8479310b9fae49a82 | |
| parent | fd85f328fc278e1594261992e1e321ff3ba42e42 [diff] | |
| parent | 4c62151f8e70b35f4927b65877a0c1d177afb921 [diff] |
[automerger skipped] Add libs that have been resolved to the library absence check. am: 4c62151f8e -s ours am skip reason: change_id I9e517d3c2344b39cf2743a34723572e646675677 with SHA1 ee30c73c63 is in history Change-Id: Id1f8c86922e6b08b8bd1681b2eecd064fcbce1f2
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.