commit | 6a35810856883cb318793a90114c1b2f7cdb2e42 | [log] [tgz] |
---|---|---|
author | Inseob Kim <inseob@google.com> | Tue Mar 19 16:44:49 2024 +0900 |
committer | Inseob Kim <inseob@google.com> | Thu Mar 21 17:18:59 2024 +0900 |
tree | 2fcadec47faf0a545b29add097fff065f1f8f690 | |
parent | b0dfb70381b729cd652a8e07b087bbb2e332e8cc [diff] |
Migrate buildinfo.sh script into Soong To build system.img in Soong, we need all artifacts including build.prop. This fully migrates buildinfo.prop file into Soong as a first step to build build.prop on Soong. Bug: 322090587 Test: compare build.prop before and after Test: build multiple times and see build.prop isn't rebuilt Change-Id: I0d5aab21a825cfe22f97a6834209f9df196625d9
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.