Skip to content
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

[Feature Request]: cargo-3ds support #3522

Closed
lexi-the-cute opened this issue Feb 24, 2024 · 5 comments
Closed

[Feature Request]: cargo-3ds support #3522

lexi-the-cute opened this issue Feb 24, 2024 · 5 comments

Comments

@lexi-the-cute
Copy link

One of the dependencies of winit cannot compile under cargo-3ds. I can't remember which one it is off the top of my head, so I'll have to try to rebuild again either tonight after work or tomorrow. I asked about it on the Nintendo Homebrew Discord (https://discord.gg/C29hYvh), but I'm not sure that have experience with Rust and Winit

I'll send more info after I test again

@lexi-the-cute
Copy link
Author

The crate is rustix

compile-log.txt

@madsmtm
Copy link
Member

madsmtm commented Feb 24, 2024

Hmm, I suspect you're gonna have trouble running Winit on the 3DS, I don't think that one uses a window managing system that Winit supports?

@notgull
Copy link
Member

notgull commented Feb 24, 2024

The 3DS uses raw frame buffers, which has been decided to be out-of-scope for winit.

@notgull notgull closed this as not planned Won't fix, can't repro, duplicate, stale Feb 24, 2024
@lexi-the-cute
Copy link
Author

what do you propose i should use instead? preferably something that's interchangeable with existing winit code so it can be easily swapped between it and winit depending on the target?

@notgull
Copy link
Member

notgull commented Feb 25, 2024

At one point we were talking about setting up a crate to deal with raw framebuffers. This also comes up when dealing with DRM/KMS on Linux, for instance. Then winit could have a backend that uses that crate to simulate a single-window environment (like a kiosk).

Admittedly this is pretty low-priority for us on the roadmap, as there are more pressing items to look into as well as very few people on the winit team who are experienced in dealing with raw framebuffers. If there is a lot of community interest then we can expedite this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants