| commit | 1af7e1fa7f8a4b35fdda1a9a1083e7db65d43231 | [log] [tgz] |
|---|---|---|
| author | Tomislav Novak <tnovak@meta.com> | Thu Sep 21 13:48:57 2023 -0700 |
| committer | Tomislav Novak <tnovak@meta.com> | Thu Sep 21 14:49:56 2023 -0700 |
| tree | f3e18627f167da01e79fed21d5b8728a0d67a091 | |
| parent | c774b33c6188cfc80f802ce65ef714af22de5971 [diff] |
emulator_arm64: Revert TARGET_NO_KERNEL to emulator default
With TARGET_NO_KERNEL set to false, sdk_phone_arm64 build depends on
$PRODUCT_OUT/kernel, which no longer exists as of aosp/2548555 ("Cleanup
in emulator_arm64/device.mk").
$ lunch sdk_phone_arm64-eng && m
[...]
FAILED: ninja: 'out/target/product/emulator_arm64/kernel', needed by
'out/target/product/emulator_arm64/boot.img', missing and no known
rule to make it
Goldfish makefiles copy prebuilt kernels to $OUT/kernel-ranchu that
the emulator then uses, so no need to generate the boot image.
Test: lunch sdk_phone_arm64-eng && m
Change-Id: I3598ac04b352fc07679315ced4f7b7a536ccb5a5
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.