commit | 3db1ef61de5d5c852430a81c02c47f513c78fc3b | [log] [tgz] |
---|---|---|
author | Håkan Kvist <hakan.kvist@sony.com> | Tue May 03 10:19:41 2022 +0200 |
committer | Håkan Kvist <hakan.kvist@sony.com> | Tue May 03 13:00:32 2022 +0200 |
tree | 50293f30d249d2b9e35ef0b0340a267304bf69ca | |
parent | e30f7e8be15e4afefbe71ec5b04410b0f8880e7b [diff] |
Only enable zucchini if configuration file exists Only enable zucchini if configuration file zucchini_config.txt exits in target files and version in source and target is the same. Without this patch zucchini would be enabled if configuration file was missing from both target files. Bug: 231204699 Test: Run ota package generation with zucchini_config.txt missing from both source and target zips. Confirm that zucchini is disabled. Change-Id: Ia34998fd911d5860b38fe49fa5a88056a22d661e
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.