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
Similar patterns have ended up in other places to work with the
prebuilt ART module, but they belong in ART.
#codehealth
Test: vendor/google/modules/ArtGoogle/build-with-prebuilt-art-module.sh droid
on internal with prebuilts from mainline_modules on git_master-art
Bug: 238426831
Change-Id: Ice7aaef6a4e8dd04723ec2d7b009eb7e6f35f5d6
Additionaly,
1. Run it as a python_binary_host so that it uses the hermetic python
toolchain
2. Fix an existing bug where if `board_info_txt` was empty, $^ would
evaluate to its own path, and it would try to parse the relevant
configuration from the wrong file
Bug: 196300985
Test: m out/target/product/vsoc_arm64/android-info.txt
Change-Id: Ie1e51a93041591829da4351dd57f37106e15d764
Documents for GSI specific packages can be found at
device/generic/common/README.md.
Bug: 254392480
Test: Presubmit
Change-Id: I03e9d66462f39c0631dfcbe16902e5978e41c8b6
Building for riscv64 without ALLOW_MISSING_DEPENDENCIES=true fails
on prebuilt modules that are missing riscv64 files. Set
ALLOW_MISSING_DEPENDENCIES=true in BoardConfig.mk for now to avoid
always having to set it on the command line.
Test: lunch aosp_riscv64-userdebug && m ndk_sysroot
Change-Id: I6b7dcf684b59d073cb6e257717946d551aefdb44
Needs to be on all (for now) devices with libcrypto, i.e. all
of them.
I failed to learn from https://r.android.com/1305853 that
adding something to Conscrypt's requirements doesn't work if
the module is coming from a prebuilt...
Again, the correct solution here would actually be to make
libcrypto rather than Conscrypt require prng_seeder but Soong
considers that a circular dependency
Bug: 243933553
Test: m installclean && m and verify prng_seeder is installed and running.
Change-Id: Ie34f8c693469eaeedae6a010b956d6c6513a6b15
Use runtime resource overlay to override SystemUI resources
in case some legacy devices might have invalid settings,
and the invalid settings might cause unexpected SystemUI
errors when installing GSI on different devices.
Bug: 245806899
Test: Build and install GSI on Pixel
Change-Id: I704ba8f1a4a1d058e5e992d3ca18bdb4bda6610d
On devices launching after Android U, we no longer install the HIDL OMX
service. It is deprecated.
Test: Build and run Cuttlefish with SHIPING_API_LEVEL 33 and 34
Bug: 218588089
Change-Id: I9a6dbffd381bdad5428e9c365bd50445a9b14a67
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
Rolling back the changes from aosp/2199179.
Bug: 243923977#comment9
Test: adb shell ls /dev/selinux /system/etc/selinux
Change-Id: If205f106230c2f076f72396011b68079ddd4d253
Since the vndk apex is introduced, same vndk variants check has stopped
when building vndk_package, and it's performed only with checkbuild.
Bug: 244654349
Test: m vndk_package
Change-Id: Iee30b5df75565c024f93d40bc6eaa7a729c2e09c
