| commit | 4a8096ef455458f067abdbd0f4c00c4a46a67619 | [log] [tgz] |
|---|---|---|
| author | Logan Chien <loganchien@google.com> | Thu Mar 21 01:29:09 2019 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Thu Mar 21 01:29:09 2019 -0700 |
| tree | c847d445328ffe4dfa5bf2d4e5946651f8c65049 | |
| parent | d97130751f5fa8fb6bcf222c78ad2dd7a66cc42e [diff] | |
| parent | d5050f82e4f5ace793136ae2d41bdf06b0ac1fb1 [diff] |
Merge "Update check_elf_file.py for clang-r353983" am: 81589605fd am: 5d00745b0a am: d5050f82e4 Change-Id: I7ca40fac3d66b2918a0c0b2e808bf5362ceb93a7
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.