commit | e46ada4f233e4ed5a88c832ee4399e7346e42f1a | [log] [tgz] |
---|---|---|
author | Adam Seaton <aseaton@google.com> | Mon Jan 14 17:25:44 2019 -0800 |
committer | android-build-merger <android-build-merger@google.com> | Mon Jan 14 17:25:44 2019 -0800 |
tree | ee7f15ccb741cad5e85e70e62af9e8b911b8ece9 | |
parent | ac6eac206d0e4b0604a362d1bcbfae3e1b03bfc2 [diff] | |
parent | 04bc1f36dad0ecc4c3ca8744997ec2562ab18ede [diff] |
[automerger skipped] [automerger] [DO NOT MERGE] Update Platform Security String to 2019-03-01 for nyc-dev Bug:122541777 am: 7a403979d6 am: e56e5efec9 am: 87877d530a am: 33ecfffc1f skipped: 440db90921 am: ed56062889 am: f583da6005 am: 04bc1f36da -s ours am skip reason: subject contains skip directive Change-Id: I6bcfe95c949d7d573eb10482f5e9694df53065e8
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.