Someone have made something simlar before

[poohzaza166]

https://github.com/brunodev85/winlator

[charlieduzstuf]

@poohzaza166 do you want to help?

[poohzaza166]

sure but i am not sure if i can bring much to the table

[charlieduzstuf]

sure but i am not sure if i can bring much to the table

want to try anyway?

any help is good help

[poohzaza166]

sure, is there a discord server?

[charlieduzstuf]

sure, is there a discord server?

No

[poohzaza166]

i see. Whats your priority right now? I saw that you made a lot of commit in the universal translation layer and you are looking to add android app support to the wine fork aswell. Are you looking to use that custom emulation layer in this Piston? or are you just aiming to run linux environment with steam with opengl and vulkan hardware acceleration?

[charlieduzstuf]

i see. Whats your priority right now? I saw that you made a lot of commit in the universal translation layer and you are looking to add android app support to the wine fork aswell. Are you looking to use that custom emulation layer in this Piston? or are you just aiming to run linux environment with steam with opengl and vulkan hardware acceleration?

Goliath is a seperate project entirely, Piston is effectively a SteamOS version of Winlator running a super optimised SteamOS instance, packaged in a way to make it look like a game library/playing app on the phone (like Geforce Now ig? ), in basic terms.

[charlieduzstuf]

@poohzaza166 Do you have any ideas?

[poohzaza166]

kinda but first a few question to make sure that we are on the same page.

1. when you are refering to SteamOS do you mean "immutable Custom version of archlinux that launch steam ui by default"?
2. Is the project main AIM is to create an android app that launch steam and steam game?

IF so ideally i always want to avoid software emulation all together. ie: running a vm inside of qemu inside of android.

I am not sure how well android handle containers like LXC or dose it even support vulkan and opengl pass through or not. Since these are, In my opinion more important to running steam game on android than the feasibility and the performance hit of translating amd64 CPU call.

ON a tangent.
DID u know that steam support running game on chrome os using chrome linux container and proton? there they managed to get opengl and vulkan working (though with a massive performance hit comparing to chroot and rooting chrome os that i have tried)

from my simple google search linux container on android i found this

I was also doing research on getting steam working on arm with panfrost driver as well but from my understanding Android have a Far better and well establish Graphical acceleration infrastructure comparing to wayland and panfrost and mesa.

what do you think?

[charlieduzstuf]

It's an instance of Linux with the Steam Client in a way similar to SteamOS, but signigicantly optimised for mobile. The aim is to open the app and go right into big picture and then run an app.

All your stuff sounds pretty good, so we can do it that way

[charlieduzstuf]

@poohzaza166 are you still in?

[amazon-q-developer]

Progress Updates

• I'll start by exploring the repository structure to understand what kind of project this is and then examine the referenced GitHub repository to understand what needs to be implemented.
• This appears to be a Rust project with Android bindings and Wayland server components. Let me examine the main Cargo.toml and README to understand the project's purpose better.
• This is a SteamOS emulator project written in Rust. Now let me check the README to understand more about the project's goals and then examine the referenced Winlator project to understand what needs to be implemented.
• Now I understand - this is "Piston", an Android app that runs a VM of SteamOS. The request mentions Winlator, which is likely a similar project for running Windows applications on Android. Let me examine the main source files to understand the current implementation.
• Now let me examine the lib.rs file to understand the core emulator implementation and then look at the Android app structure to understand how it integrates.
• Now let me examine the Android app structure to understand how the Rust emulator integrates with the Android frontend.
• Let me examine the main Android activity and the native interface to understand how the current implementation works.
• Now let me examine the native interface to understand how the Rust code is called from Java.
• Now let me examine the android-bindings crate to understand how the Rust code interfaces with Android.
• It seems the android-bindings source directory is missing. Let me check if there are any missing workspace members and examine the compositor-core and wayland-server components to understand the architecture better.
• Analyzing the current project structure and understanding what needs to be implemented based on Winlator reference
• I need to implement missing components for a SteamOS emulator Android app, similar to how Winlator runs Windows apps on Android. The project has a Rust core emulator, Android bindings, and an Android frontend, but several key components are missing or incomplete.
• Based on my analysis and the plan, I'll start implementing the missing components. First, I'll create the missing android-bindings source code and the graphics-pipeline crate, then implement the core emulator modules.
• Now I need to update the android-bindings Cargo.toml to include the missing dependencies and create the graphics-pipeline crate that's referenced in the workspace.
• Now I'll create the missing graphics-pipeline crate that's referenced in the workspace.
• Now I need to create the remaining stub modules for the graphics pipeline and then implement the missing modules in the main emulator core.
• Now I need to implement the missing modules in the main emulator core that are referenced in lib.rs but don't exist as files.

---

✅ I finished the proposed code changes, and the pull request is ready for review: #13.

Comment on the pull request to provide feedback and request a new iteration.

To provide feedback on how Amazon Q Developer performed with code generation, create an issue in the Amazon Q Developer public repository.