| commit | f3922402cb30cf4d419acad3e21cdf7d8edda961 | [log] [tgz] |
|---|---|---|
| author | Yumi Yukimura <me.cafebabe@gmail.com> | Tue Mar 19 02:51:42 2024 +0800 |
| committer | Jan Altensen (Stricted) <info@stricted.net> | Tue Jul 02 00:26:22 2024 +0000 |
| tree | 0138862034abe48b962f2479d56e75669782e257 | |
| parent | 26afa6d38a151c8a4acce0e28564d47f7713849d [diff] |
build: Enable super image build rules depending on single super block device * The current logic does not suit for multiple block devices case, it generates split images hence output dir shall be specified * Multiple block devices is possible with non-RDAP too, and it could work for RDAP with single block device, so it's incorrect to depend on RDAP flag Change-Id: I8563b96b35351ef0a3b40ae172c2e904ee57f85e
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.