commit | 15b89d8fcdc5065ad96b36a5fb1ca662dc44c080 | [log] [tgz] |
---|---|---|
author | Steven Moreland <smoreland@google.com> | Thu Dec 23 22:18:42 2021 +0000 |
committer | Steven Moreland <smoreland@google.com> | Thu Dec 23 22:18:42 2021 +0000 |
tree | 4b0eb33145133f2a05b9cae4d1be5042a40f8c44 | |
parent | 46c84edacf8b1fd0adc85a50ab59ee8f8c1e7b66 [diff] |
Don't require current.txt order. There have been a lot of merge conflicts because of this file (and a few cases of people needing to merge changes internally because of it). Though, we really don't care about the order of the file. So, compare ignoring order. If there is a merge conflict in the future, we can change the order slightly, and we can gradually clean up the order over time, as needed (really, it's not important). Bug: N/A Test: file reordered as build-time check Change-Id: I955a2bd78872ff6d975bc494f10b2ed5e532c680
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.