the sidecar issue in GSI was fixed.
Bug: 111538404
Test: presubmit
Change-Id: Ia48ce2e076edc4f13f85e58d9bbbe15b8e6a4438
Signed-off-by: Roman Kiryanov <rkir@google.com>
Revert submission 2529481-aosp-no-emulator
Reason for revert: DroidMonitor: Potential culprit for Bug 280642806 - verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.
Reverted changes: /q/submissionid:2529481-aosp-no-emulator
Change-Id: I732e1b1a1f001fe016a4e20c1a95516995522501
The gsi_release.mk should be agnostic of AOSP or Android. In case of
Android builds, modules should be prebuilt, however in the case of AOSP
they can be built from source. This option should now be configured at
the product makefile level
Also update the shipping API to 34
Bug: 278607630
Test: TARGET_PRODUCT=gsi_arm64 TARGET_BUILD_VARIANT=userdebug build/soong/soong_ui.bash --dumpvar-mode MODULE_BUILD_FROM_SOURCE
returns true
TARGET_PRODUCT=gsi_arm64 TARGET_BUILD_VARIANT=userdebug MODULE_BUILD_FROM_SOURCE=false build/soong/soong_ui.bash --dumpvar-mode MODULE_BUILD_FROM_SOURCE
returns false
Change-Id: I5937764d8df307ed7547363e6ba2742828779282
Remove the hacks that prevent building the rest of the platform
for aosp_riscv64.
Test: lunch aosp_riscv64-userdebug && m
Change-Id: Id8b48c8c456e76624647f153c7dd9612569fc7a1
Bug: 206676167
Test: Verified during boot that frameworks skips loading of rs_jni by
injecting logs into frameworks/base/rs.
Change-Id: I856367df816c8ad28dde54af69ab36e4f1605146
aosp_riscv64 doesn't use base-system.mk yet, add init_first_stage
to the ramdisk manually.
Test: lunch aosp_riscv64-userdebug && m out/target/product/generic_riscv64/ramdisk.img
Change-Id: I148e436b34e8900815eb8dac42a6c1f5251f824d
Uncomment everything in aosp_riscv64.mk that doesn't break the
aosp_riscv64-userdebug build.
Test: m droid dist
Change-Id: I29b07d74fb8e93848bd422287e9cfaa32bde6d93
init.environ.rc has a postinstall command to create the symlinks in
and directories in the root filesystem. Without those packaging
target-files.zip fails with:
failed to find system in canned fs_config
Bug: 250918230
Test: lunch aosp_riscv64-userdebug && m installclean && m droid dist
Change-Id: Iccb6ba53a3caa918431119230256a01d4919f1cc
Using init instead of init_system causes a failure packaging
target-files.zip:
failed to find system in canned fs_config
Switching to init_system seems to fix it.
Test: lunch aosp_riscv64-userdebug && m droid dist
Change-Id: Ia2cf2ef1b85c2e63076f70132f2cce64828c5c93
`m droid dist` fails on hiddenapi rules missing bootclasspath classes,
add default_art_config.mk to set PRODUCT_BOOT_JARS, and then override
PRODUCT_USES_DEFAULT_ART_CONFIG back to false to avoid a dependency
from the boot.zip dist artifact to dex2oat, which doesn't work for
riscv64 yet.
Test: lunch aosp_riscv64-userdebug && m droid dist
Change-Id: Icc332ee9132568251386ec742932f6708312bb92
Disable most of the inherited product makefiles so that `m droid`
passes, and then add back a few working packages to PRODUCT_PACKAGES.
Test: lunch aosp_riscv64-userdebug && m droid
Change-Id: Ifbc4758735ec29876cbdd5a2ec97dd99aaebc210
Add barebones files to support building for a riscv64 target.
Bug: 250918230
Test: lunch aosp_riscv64-userdebug && m ALLOW_MISSING_DEPENDENCIES=true nothing
Change-Id: I61e6ecf6706b7682c77b07e6593d78c7d1eaef39
