commit | 77a08b4fb2e09e39f29f6f3625ed0107f73e27a8 | [log] [tgz] |
---|---|---|
author | Calin Juravle <calin@google.com> | Thu Jan 31 09:32:17 2019 -0800 |
committer | android-build-merger <android-build-merger@google.com> | Thu Jan 31 09:32:17 2019 -0800 |
tree | f547c4da13104128f8b58718b531ba4cb147d065 | |
parent | bdd4b9d78a94a9f143a785e0034665ba75e4a8ba [diff] | |
parent | 536c2d3de8c719210df163a558e1f052a6c91c76 [diff] |
Merge "Count hotness in system server compiled code" am: 4f3f03c09b am: 536c2d3de8 Change-Id: Ia7bc1f27df44647b725c13620ca7fa4472593b35
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.