fix: update workspace Cargo.toml, README.md workspace distinctions

This commit is contained in:
Ryan Walters
2025-09-16 09:18:24 -05:00
parent a3c4c94d42
commit d0ee7db2ef
4 changed files with 11 additions and 7 deletions

2
Cargo.lock generated
View File

@@ -712,7 +712,7 @@ checksum = "42f5e15c9953c5e4ccceeb2e7382a716482c34515315f7b03532b8b4e8393d2d"
[[package]] [[package]]
name = "pacman" name = "pacman"
version = "0.80.3" version = "0.81.0"
dependencies = [ dependencies = [
"anyhow", "anyhow",
"bevy_ecs", "bevy_ecs",

View File

@@ -3,12 +3,15 @@ members = ["pacman"]
resolver = "2" resolver = "2"
[workspace.package] [workspace.package]
version = "0.1.0" authors = ["Xevion"]
edition = "2021" edition = "2021"
authors = ["Xevion <xevion@xevion.dev>"] readme = true
license = "MIT" homepage = "https://pacman.xevion.dev"
repository = "https://github.com/Xevion/Pac-Man" repository = "https://github.com/Xevion/Pac-Man"
description = "A Pac-Man game written in Rust" license = "GPL-3.0-or-later"
keywords = ["game", "pacman", "arcade", "sdl2"]
categories = ["games", "emulators"]
publish = false
[workspace.dependencies] [workspace.dependencies]
# Common dependencies that might be shared across crates # Common dependencies that might be shared across crates

View File

@@ -85,7 +85,8 @@ You can read the [roadmap](ROADMAP.md) file for more details on the project's go
Since this project is still in progress, I'm only going to cover non-obvious build details. By reading the code, build scripts, and copying the online build workflows, you should be able to replicate the build process. Since this project is still in progress, I'm only going to cover non-obvious build details. By reading the code, build scripts, and copying the online build workflows, you should be able to replicate the build process.
- Install `cargo-vcpkg` with `cargo install cargo-vcpkg`, then run `cargo vcpkg build` to build the requisite dependencies via vcpkg. - Install `cargo-vcpkg` with `cargo install cargo-vcpkg`, then run `cargo vcpkg build --manifest-path pacman/Cargo.toml` to build the requisite dependencies via vcpkg.
- `--manifest-path` is only required if you run it from the root directory; you can omit it if you `cd` into the `pacman` directory first.
- This is only required for the desktop builds, not the web build. - This is only required for the desktop builds, not the web build.
- We use rustc 1.86.0 for the build, due to bulk-memory-opt related issues on wasm32-unknown-emscripten. - We use rustc 1.86.0 for the build, due to bulk-memory-opt related issues on wasm32-unknown-emscripten.
- Technically, we could probably use stable or even nightly on desktop targets, but using different versions for different targets is a pain, mainly because of clippy warnings changing between versions. - Technically, we could probably use stable or even nightly on desktop targets, but using different versions for different targets is a pain, mainly because of clippy warnings changing between versions.

View File

@@ -1,6 +1,6 @@
[package] [package]
name = "pacman" name = "pacman"
version = "0.80.3" version = "0.81.0"
authors = ["Xevion"] authors = ["Xevion"]
edition = "2021" edition = "2021"
rust-version = "1.86.0" rust-version = "1.86.0"