commit | cbf67e8864b0ebece76c6fdb5c11dd68c160ec66 | [log] [tgz] |
---|---|---|
author | Tri Vo <trong@google.com> | Tue Feb 05 14:08:54 2019 -0800 |
committer | android-build-merger <android-build-merger@google.com> | Tue Feb 05 14:08:54 2019 -0800 |
tree | 74b649fb59df87ef4f3a091949d291ab7c1abafb | |
parent | 4848b3238d8af684f8f61b7c3a652800c10a282f [diff] | |
parent | 5a3d3acce8e7881f529c7b91f36ef9ffe67a9a62 [diff] |
Merge "Add ashmemd to base_system.mk" am: 7bd32730a4 am: 07e5189064 am: 5a3d3acce8 Change-Id: I1b7b45b1ef1bad377ee1e1a7258d3f7b7110bc50
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.