+++ title = "This Month in Rust GameDev #52 - June 2024" transparent = true date = 2024-07-03 draft = true +++
Welcome to the 52th issue of the Rust GameDev Workgroup's monthly newsletter. Rust is a systems language pursuing the trifecta: safety, concurrency, and speed. These goals are well-aligned with game development. We hope to build an inviting ecosystem for anyone wishing to use Rust in their development process! Want to get involved? Join the Rust GameDev working group!
You can follow the newsletter creation process by watching the coordination issues. Want something mentioned in the next newsletter? Send us a pull request. Feel free to send PRs about your own projects!
- Announcements
- Game Updates
- Engine Updates
- Learning Material Updates
- Tooling Updates
- Library Updates
- Popular Workgroup Issues in GitHub
- Other News
- Meeting Minutes
- Discussions
- Requests for Contribution
- Jobs
- Bonus
- Future news
The Playdate console
Rusty Playdate (GitHub, Mastodon) by @boozook is the large set of crates with bindings, toolset for the full cycle of creating games for the Playdate handheld console.
Big part of the Rusty Playdate project is the cargo-playdate tool (Crates.io, GitHub)
that helps to build games for Playdate hardware or a simulator. It works as a cargo-plugin as well as standalone.
The tool
- manages the compilation of your program,
- builds assets for the crate and its dependencies,
- generates a manifest,
- and assembles it all into a bundle that runs on the device or a simulator.
In this month cargo-playdate v0.5 has been released and received massive refactoring, bugfixes and new features:
- support of cargo's auto-targets (targets such as
binorexamplethat aren't declared in the Cargo.toml) - target-specific package-info inheritance from the main package-info
package.metadata.playdate.optionsinheritance from theworkspace.metadata- incremental builds now work as expected - fixed an old problem where the tool corrupts cargo's cache, which triggered full rebuild
The register decoder in the pd-symbolize-crashlog was also updated.
It now it properly decodes all available registers such as
PSR,
CFSR, and
HSFR.
See all meeting issues including full text notes or join the next meeting.
Editing this newsletter wouldn't be possible without your contributions. Thanks to everyone who helped us this month!
If you want something mentioned in the next newsletter, send us a pull request.
You can also get an early look at pending issues for the next newsletter.
That's all news for today, thanks for reading!
Also, subscribe to our socials if you want to receive fresh news!
- X/Twitter: @rust_gamedev
- Mastodon: @rust_gamedev
- Reddit: /r/rust_gamedev