commit | 6c68c5a3d4b1c61c6ec53def888c4fec870199ce | [log] [tgz] |
---|---|---|
author | Spandan Das <spandandas@google.com> | Tue Oct 22 00:21:36 2024 +0000 |
committer | Spandan Das <spandandas@google.com> | Fri Nov 01 18:26:19 2024 +0000 |
tree | 6036af0923ed19a5ae625268256c3307c33f9556 | |
parent | e4849e87ab660b59a6501b3928693db065ee873b [diff] |
Export BUILDING_ODM_IMAGE to soong If true, soong will autogenerate a partition module for odm.img Bug: 376755916 Test: verified that a odm partition soong module is created by build/soong/fsgen Change-Id: I3b286cbe06122a6ed52ad209f40154f43c1bb46c
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.