| commit | ffd8f6e439168b0f64b6b3c1523fc66bae462091 | [log] [tgz] |
|---|---|---|
| author | Tao Bao <tbao@google.com> | Wed Jan 17 02:04:32 2018 +0000 |
| committer | android-build-merger <android-build-merger@google.com> | Wed Jan 17 02:04:32 2018 +0000 |
| tree | ce9beedf2c8afd9704ff46b234a1e9a40cf4df1a | |
| parent | 5f670877ec9c4358f309c3be8f710d07e1678338 [diff] | |
| parent | efbd0f881c6bd1014e79761b9bfc8e3c31335430 [diff] |
Merge "releasetools: Consolidate the codes that generate metadata dict." am: 676c20f285 am: efbd0f881c Change-Id: Ic47fdf387ed31ad5da3e1392be5d8f5511e31cb3
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.