New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing dependency when building images for Raspberry Pi 4 #225
Comments
Would love to know the answer to this as well, trying to get it working on a Raspberry Pi too. |
The solution should be in one of the makefiles, but which one? |
Coming from https://github.com/remote-android/redroid-doc, as I've tried to launch Android apps on Raspberry Pi OS that way. It is super slow for me for some reason, but what I've managed to understand is that it actually uses Broadcom V3D driver, which means redroid's image builds it successfully. Where exactly I\anyone else should take a look to compare both makefiles, to check what might be wrong? |
Sorry to hijack this thread but I was trying to use anbox on my raspberry pi 4B 8Gb and I was answering someone who was stuck when compiling anbox but at the end it didn't work eitheir for me (https://forums.raspberrypi.com/viewtopic.php?p=1977269#p1977269) . Someone suggested me to have a look at waydroid so my questions are:
|
probably one which builds the android image for waydroid i would guess ? |
Should be working now (please note that Impish is now EOL and as such not supported anymore) |
did you get this working - I am trying to do pi 4 64 bit os with waydroid but I am struggle to get it installed - any help would be very grateful |
On a headless Raspberry Pi 4 with Ubuntu Impish (21.10), I got sway/wayvnc running. Also, I successfully installed and initialized waydroid Hirsute (21.04). Unfortunately, it doesn’t run:
And:
So I was told by @erfanoabdi in a post on Telegram: “for rpi waydroid images need to get rebuilt btw”
He then proceeded:
“with some patches on gralloc and a flag”
“revert this waydroid/android_hardware_waydroid@baa694d”
“and add TARGET_USE_V3D := true and TARGET_USE_V3D_KMSRO := true to device tree”
I don’t really know what I’m doing here, and please correct me if I’m wrong. What I already did on Ubuntu 21.10:
First of all I set up a x64 machine with Ubuntu 21.10.
Initially I wanted to build on the Raspberry Pi. However, the Android build environment does not support aarch64 out of the box, and changing that looks painful, according to some documentation that I found:
Enabling aarch64 as a host architecture for Android Build (WIP)
C/C++ Toolchain for Android Build on aarch64 (WIP)
Set up build environment and configure Git. Repo I installed manually:
Also, I installed packages listed in Google’s article Establishing a Build Environment:
Plus:
Added
vir_opt_constant_alu.c
tolibbroadcom_compiler_files
in:Not necessary, already in!
Restarted the shell, to get to the latest environment.
Configured Git.
Configured and built:
Add
TARGET_USE_V3D := true
andTARGET_USE_V3D_KMSRO := true
near top to:And near the end here:
Then:
At the very last step, the linker gives me an error about a missing dependency – see below. Any idea how to fix that?
The text was updated successfully, but these errors were encountered: