| commit | f71d68de18e84c71a8ce0ef06f48f3d07745a018 | [log] [tgz] |
|---|---|---|
| author | Søren Gjesse <sgjesse@google.com> | Tue Mar 13 16:58:45 2018 +0100 |
| committer | Søren Gjesse <sgjesse@google.com> | Wed Mar 14 22:09:10 2018 +0100 |
| tree | 423336f6b78d5cf9d04918747fd0256a09cff180 | |
| parent | 017a894c6e3bf72ddfaa43527ccd8eb386207c4e [diff] |
Enable R8 by default (second attempt for Q) Fixed bugs which was discovered in the last attempt. Bug: 74508478 Test: m -j PRODUCT-taimen-userdebug Test: m -j PRODUCT-elfin-userdebug Test: Check that some .vdex files built have R8 generated code (cherry picked from commit a3b796d9981495bdca7e41b73e4a85d507856b58) Change-Id: Ibe08137cd6db94b1fc487267e169d3f5ee598846 Merged-In: I2a8e0e5cad1d698ae73ba152e34a08a496112d7d
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.