commit | c6a8813d4419eeaad28b79c0abcc4875975b0c1d | [log] [tgz] |
---|---|---|
author | Paul Scovanner <pscovanner@google.com> | Fri Jun 14 14:16:25 2019 -0700 |
committer | android-build-merger <android-build-merger@google.com> | Fri Jun 14 14:16:25 2019 -0700 |
tree | 422d7ee4b952c21f82a030b4194c5f9b87a1e652 | |
parent | f3b955dceba82b2ebebd484fd1ba7fc7613bf410 [diff] | |
parent | 76a112e02d1e457d1fff4402c0d2c67b0732916a [diff] |
Update Security String from 08-05 to 2019-08-01 Bug:126590667 am: ead61ed19e am: ef7c2c7915 am: c639959061 am: 76a112e02d Change-Id: I57487c3748f1d900f6e6f649003e092896b893df
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.