commit | c0d7f6ed8ba17e77664204b52b40cb8267f03d0a | [log] [tgz] |
---|---|---|
author | Dan Willemsen <dwillemsen@google.com> | Tue Feb 27 13:27:54 2018 -0800 |
committer | Dan Willemsen <dwillemsen@google.com> | Mon Apr 16 15:51:51 2018 -0700 |
tree | 5c44d147adc6ba169e09f18d9b0eb01e8dba5ba3 | |
parent | b873817b9cdecf02be8eda2ed238aa34f7c810f7 [diff] |
Don't use export with BUILD_ID It's not necessary, and all the tools that read this file have been updated. Bug: 73959648 Test: cs for uses Change-Id: Ic203e83ab437beecf07760660f2b3ac7c67e9ded
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.