Headless VNC libretro frontend
Go to file
Lily Tsuru ad634bf1fa retro_frontend: actually implement variable storage
I'm not certain I'll keep it like this (it should probably be in `FrontendInterface`, so the driver code can serialize how it sees fit, rather than us), but it works to get it done.

There's also a lot of janky code I need to clean up before I'm really happy about it.
2024-08-04 06:59:31 -04:00
crates retro_frontend: actually implement variable storage 2024-08-04 06:59:31 -04:00
.editorconfig Initial commit 2024-08-02 03:20:29 -04:00
.gitignore Initial commit 2024-08-02 03:20:29 -04:00
.rustfmt.toml Initial commit 2024-08-02 03:20:29 -04:00
Cargo.lock retro_frontend: actually implement variable storage 2024-08-04 06:59:31 -04:00
Cargo.toml Initial commit 2024-08-02 03:20:29 -04:00
LICENSE Initial commit 2024-08-02 03:20:29 -04:00
README.md add disclaimer to readme 2024-08-02 03:42:06 -04:00

retrovnc

a headless Libretro frontend that exports a VNC server.

This is mostly a "fun project", and probably isn't a very great solution for remote gaming.

Dependencies

  • A C++ toolchain
  • A Rust toolchain.
  • Maybe libvncserver (i'm not sure, it seems like the package can build it).

Building

$ cargo b --release

Usage

$ retrovnc --core <CORE> --rom <ROM>

For disc-based titles it is probably a good idea to pass the cuesheet file. I will implement stuff later to make this less annoying.