| commit | bd3dd7e4e4796a9005fd2a494fcfe07ce72506ec | [log] [tgz] |
|---|---|---|
| author | Jerome Gaillard <jgaillard@google.com> | Mon Oct 21 05:08:48 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Mon Oct 21 05:08:48 2019 -0700 |
| tree | 568390ed42ef0a4b5b05df63300746a679dd11d6 | |
| parent | 7f7c2ca4a93625ae88f5441c3b935b3699a935c1 [diff] | |
| parent | 8d0419cb6c7450f7e9dc05b2c486f1841543c77a [diff] |
Merge "Allow files generated by droidstubs to be copied in the SDK" am: aa1c6bb4b3 am: fac0ac32f9 am: 8d0419cb6c Change-Id: Ib0abd57898d07f8b4f075c5a522d6c528bce8e8b
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.