| commit | aeca4e212ebb760d664f771811b641b2be384034 | [log] [tgz] |
|---|---|---|
| author | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Fri Feb 28 21:26:54 2020 +0000 |
| committer | Julien Desprez <jdesprez@google.com> | Thu Apr 09 08:15:37 2020 -0700 |
| tree | c2d4abb14bc6dda98a0d38428215dbb2774b35e8 | |
| parent | 870dbc02c9f2310b02c2e9fbd952099d73bb2c7e [diff] |
Move build number file to out/soong Move the build number file to out/soong so Soong can treat it as an output path, and pass the name of the file to Soong instead of the command to read it. Test: m checkbuild Change-Id: I9e1aecf33d11fe4fde34cd57cc9b1f1ad49b0424 Bug: 153071808 Merged-In: I9e1aecf33d11fe4fde34cd57cc9b1f1ad49b0424
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.