commit | 8376b32e429d0da671c6813a149938dc92685ece | [log] [tgz] |
---|---|---|
author | Kiyoung Kim <kiyoungkim@google.com> | Fri Jun 21 14:15:49 2024 +0900 |
committer | Kiyoung Kim <kiyoungkim@google.com> | Tue Jul 02 02:22:51 2024 +0000 |
tree | 443a7c84a8537af730b7ad04d0bed112ec8b52ed | |
parent | 14d19661a00cf559a4c23305277c16ffa00660a1 [diff] |
Generate system diff between KATI and SOONG There is an effort to generate system image with Soong, but there are some difference in installed files between Soong defined system image and KATI defined one. This change generates diffs between installed files from two sources. Bug: 346873717 Test: USE_SOONG_DEFINED_SYSTEM_IMAGE=true m -j on aosp_cf_x86_64 generated diff file. Change-Id: I25c71f88d16a4efb873c21abe70ca9c41c6423ca Merged-In: I25c71f88d16a4efb873c21abe70ca9c41c6423ca
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.