sdl12-compat VS crates.io

I'm just glad so many of the SDL 1.2.x-era games dynamically linked SDL so I can use sdl12-compat to stick them on top of SDL 2.x's non-modesetting fullscreening and PulseAudio support.

Thankfully, most people don't statically link SDL 1.2, so it's possible to use sdl12compat to rebase them on top of SDL 2.x's non-modesetting fullscreening support, among other things.

There have been some efforts to keep them working: http://www.improbability.net/loki/ https://github.com/libsdl-org/sdl12-compat/

I've been determined to get the only system not on the device working in some way. The biggest issue to the Apple II systems not being present is that all the emulators are not written in SDL2 and the only Apple II emulator written in SDL2 (shamusworld) is far from perfect. So I tried my hand at something: What if I could wrap SDL1.2 to SDL2 against linapple? My brother showed me on github sdl12-compat https://github.com/libsdl-org/sdl12-compat. Amazingly enough, we have results. Now it's not going to be as functional this way like having RetroArch to configure things, but I have over twenty Apple II games pre-configured with controls thus far.

You need this compatibility library and you can drop it into the "lib" folder in the game files.

Here's the only useful link from the article: https://github.com/libsdl-org/sdl12-compat/releases/tag/release-1.2.52

It looks like the multiple monitor issue was known and theoretically fixed? https://github.com/libsdl-org/sdl12-compat/issues/38

Really old Linux games based on SDL1 can also work on Wayland by using the SDL1 on SDL2 wrapper in combination with a recent SDL2 build (I've been successful with Psychonauts this way, and it even solved some weird windowing problems with the game)

Rust has a rich ecosystem of frameworks and libraries that let you read, parse, and manipulate text files, interact with cloud services and databases, and perform any other job that your project's development workflow may require. And because of its strong typing and tight memory management, you are much less likely to write programs that behave unexpectedly in production.

All the code discussed in this article can be accessed through this repository. For integration with existing projects consider using keyword_extraction crate available on crates.io.

So, be sure to double-check your critical libraries and be sure their alternatives exist in the Rust ecosystem. There’s a good chance the crates you need are available in Rust's crates.io repository.

The previous section was very simple, this section is also very simple but introduces us to cargo which is Rust's package manager, as a JS dev my mind goes straight to NPM.

Now, there has to be a place where all these packages come from. Similar to npmjs registry, where all node packages are registered, stored and retrieved, Rust also has something called crates.io where many helpful packages and dependencies are registered.

Before proceeding, let's check https://crates.io/, the official Rust package registry.

The most thrilling aspect has been the joy of writing the backend. It's like every struct, enum, and method in Rust forms this interconnected Multiverse of code , which you can see in crates.io which is best Documentation experience I Ever Had.

5. Crates.io

When using crates from eg. crates.io, and also things like std and core

Vendoring your packages was very tedious to even remotely get to work with Cargo. I spent a very long time getting Cargo to work together with cargo-local-registry. We vendor crates from crates.io and a custom internal registry.