| commit | 0abdb5811d220f6e1a28d114a46cb76306a4a3ff | [log] [tgz] |
|---|---|---|
| author | Nan Zhang <nanzhang@google.com> | Tue Feb 20 17:00:39 2018 -0800 |
| committer | Nan Zhang <nanzhang@google.com> | Wed Feb 21 14:12:18 2018 -0800 |
| tree | 030f30588b35cb92ff5b512826e12e071111b740 | |
| parent | 5ef78033d5cc5790f4efd75769dd7fba4ccf477a [diff] |
Use BUILD_NUMBER_FROM_FILE instead of BUILD_NUMBER in Make. <Two phase commits> Since internal master code has more places that use BUILD_NUMBER (mostly in vendor/) than AOSP (conflict). We can't deprecate BUILD_NUMBER directly. Therefore, we try to switch to BUILD_NUMBER_FROM_FILE as much as possible at first. Then we will do a one-off deprecation for BUILD_NUMBER in internal master next step. Test: m -j Bug: b/70351683 Change-Id: I14ffee7381933c9fde14c4bde8c0c14e45fe98bf
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.