Headless VNC libretro frontend
Go to file
Lily Tsuru d4329be132 refactoring
Removes the frontend glue module, instead the frontend state struct is allowed to be created by users. This doesn't solve Rust 2024 problems (although, since we're building c++ code anyways, we can always just stash the pointer there) but it's much cleaner.Some stuff is made to use pointers, this is just because I don't want to mess around with lifetime stuff right now (it all lasts as long as the app anyways)
2024-08-04 02:02:29 -04:00
crates refactoring 2024-08-04 02:02:29 -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 refactoring 2024-08-04 02:02:29 -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.