| commit | 394dcde3ac0cdad32ceda3231895e6d8655aa8f4 | [log] [tgz] |
|---|---|---|
| author | yangbill <yangbill@google.com> | Thu Jul 26 19:07:50 2018 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Thu Jul 26 19:07:50 2018 -0700 |
| tree | bea9e2f4da64721b90b38e42e50ed9b78faec30a | |
| parent | 0a57030ec485448fbdb7a02af0da9d3f0322cf8d [diff] | |
| parent | c9091eb3a0e707adc0ddf392bcd7967b3d1cef21 [diff] |
Merge "ATest: Sync auto_test_config for multilib modules" am: f2bea1b296 am: 7e7f79c138 am: aa595dc2bb am: c9091eb3a0 Change-Id: I202ca6ca365cf753b8c75e28a196037572b921d9
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.