xtasks are effectively like shell scripts written in Rust. As they only require rustc and cargo, they solve most portability problems (see for example #2859). They also allow using any Rust crates as part of the build automation, so for example they could pull the wasm-opt crate as a dependency, instead of having this comment instructing the user to install it manually:
|
# to get wasm-opt: apt/brew/dnf install binaryen |
|
wasm-opt "docs/${CRATE_NAME}_bg.wasm" -O2 --fast-math -o "docs/${CRATE_NAME}_bg.wasm" # add -g to get debug symbols |
So it could make the repository easier to work with for new contributors.
xtasks are effectively like shell scripts written in Rust. As they only require rustc and cargo, they solve most portability problems (see for example #2859). They also allow using any Rust crates as part of the build automation, so for example they could pull the wasm-opt crate as a dependency, instead of having this comment instructing the user to install it manually:
egui/sh/build_demo_web.sh
Lines 81 to 82 in eb0812a
So it could make the repository easier to work with for new contributors.