wgpu/naga/xtask/Cargo.toml

[package]
name = "xtask"
version = "0.1.0"
edition = "2021"
publish = false

[dependencies]
anyhow = "1"
env_logger = { version = "0.10.0", default-features = false }
glob = "0.3.1"
hlsl-snapshots = { path = "../hlsl-snapshots"}
indicatif = "0.17"
jobserver = "0.1"
log = "0.4.17"
num_cpus = "1.16"
pico-args = "0.5.0"
shell-words = "1.1.0"
which = "4.4.0"

[workspace]
build: move from `make` to `cargo xtask` workflows Re-implement `naga` development workflows using [`cargo xtask`]. Convert `make` logic and shader test configuration as file with Bash variables into an `xtask` crate and YAML files, respectively. Pros: * We now have a _portable_ workflow everywhere, which means Windows folks and people who don't install `make` don't have to suffer. 😮‍💨 * Workflow logic is now relatively easy to inspect and change. Whew! 💁🏻‍♂️💦 * Contributors can use their existing Rust knowledge to contribute to developer experience. 🎉 * `cargo xtask` is a relatively well-known convention for workflows in the ecosystem. * We can do fancy things like allow folks to run at different log levels for workflows, depending on their tastes. Cons: * There's now a non-trivial compile step to project workflow. Incremental rebuilds seem to be pretty short, though! * Code is much more verbose than the (very) terse `make` implementation. [`cargo xtask`]: https://github.com/matklad/cargo-xtask 2023-03-20 14:42:39 +00:00			`[package]`
			`name = "xtask"`
			`version = "0.1.0"`
			`edition = "2021"`
			`publish = false`

			`[dependencies]`
			`anyhow = "1"`
			`env_logger = { version = "0.10.0", default-features = false }`
			`glob = "0.3.1"`
Fix installing naga-cli from git (#2398) Move hl-snapshots out from the xtask workspace, since it's also used as a dev dependency in the naga crate itself for a test. 2023-07-07 23:33:48 +00:00			`hlsl-snapshots = { path = "../hlsl-snapshots"}`
[naga xtask] Use `indicatif` crate to report validation progress. 2023-12-19 21:50:42 +00:00			`indicatif = "0.17"`
[naga xtask] Run validation jobs in parallel, using jobserver. 2023-12-19 21:51:08 +00:00			`jobserver = "0.1"`
build: move from `make` to `cargo xtask` workflows Re-implement `naga` development workflows using [`cargo xtask`]. Convert `make` logic and shader test configuration as file with Bash variables into an `xtask` crate and YAML files, respectively. Pros: * We now have a _portable_ workflow everywhere, which means Windows folks and people who don't install `make` don't have to suffer. 😮‍💨 * Workflow logic is now relatively easy to inspect and change. Whew! 💁🏻‍♂️💦 * Contributors can use their existing Rust knowledge to contribute to developer experience. 🎉 * `cargo xtask` is a relatively well-known convention for workflows in the ecosystem. * We can do fancy things like allow folks to run at different log levels for workflows, depending on their tastes. Cons: * There's now a non-trivial compile step to project workflow. Incremental rebuilds seem to be pretty short, though! * Code is much more verbose than the (very) terse `make` implementation. [`cargo xtask`]: https://github.com/matklad/cargo-xtask 2023-03-20 14:42:39 +00:00			`log = "0.4.17"`
[naga xtask] Run validation jobs in parallel, using jobserver. 2023-12-19 21:51:08 +00:00			`num_cpus = "1.16"`
build: move from `make` to `cargo xtask` workflows Re-implement `naga` development workflows using [`cargo xtask`]. Convert `make` logic and shader test configuration as file with Bash variables into an `xtask` crate and YAML files, respectively. Pros: * We now have a _portable_ workflow everywhere, which means Windows folks and people who don't install `make` don't have to suffer. 😮‍💨 * Workflow logic is now relatively easy to inspect and change. Whew! 💁🏻‍♂️💦 * Contributors can use their existing Rust knowledge to contribute to developer experience. 🎉 * `cargo xtask` is a relatively well-known convention for workflows in the ecosystem. * We can do fancy things like allow folks to run at different log levels for workflows, depending on their tastes. Cons: * There's now a non-trivial compile step to project workflow. Incremental rebuilds seem to be pretty short, though! * Code is much more verbose than the (very) terse `make` implementation. [`cargo xtask`]: https://github.com/matklad/cargo-xtask 2023-03-20 14:42:39 +00:00			`pico-args = "0.5.0"`
			`shell-words = "1.1.0"`
			`which = "4.4.0"`

			`[workspace]`