Skip to content

Conversation

playfulFence
Copy link
Contributor

closes #242
We probably want to use m1 runner for this to actually have any impact (?)

@playfulFence playfulFence added the skip-changelog No changelog modification needed label Oct 16, 2025
@playfulFence
Copy link
Contributor Author

It's either me dancing the cargo-batch dance wrong, or @bugadani being right about the fact that it needs to be executed on m1 runner to have any positive difference in build time

https://github.com/playfulFence/esp-generate/actions/runs/18558236275

Comment on lines +78 to +80
if ! command -v cargo-batch &> /dev/null; then
cargo install --git https://github.com/embassy-rs/cargo-batch cargo --bin cargo-batch --locked --force
fi
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We shouldn't do this on the normal runners, the xtask should detect if cargo-batch is present and fall back to individual cargo commands otherwise, just like we do for esp-hal. forcing cargo-batch is not the best idea (what if you simply don't want it on your PC, or what if your antivirus decides to remove it suddenly?), we have the code to somewhat smartly generate the commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-changelog No changelog modification needed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

(Try to) use cargo-batch to reduce build time

3 participants