Discussion on "Cross-Compiling 10,000+ Rust CLI Crates Statically"

Ajam · 2025-06-26T13:13:14.698Z

🤖 AI translation tools were used to assist with language clarity, as our research team are not native English speakers. We believe the quality of our research and findings will speak for themselves Pkgforge hosts the world's largest collection of ...

I wonder if using --all-features also brought in more system or architecture dependencies, leading to more failures?

We use the --all-features flag because some crates don't produce an executable unless we specifically use the --feature flag.

We couldn't find an easy way to determine what features produced an executable, so decided to use --all-features directly.

What you hypothesize is actually true. We notice some errors were due to us using this --all-features flag.

In a future update, I will write a resolver which will resolve and use the correct feature flag automatically. But that's far in the future.

Ajam A simple first step could be: try with all features, and if that fails for any reason, try with default features.

teor The problem is, it won't fail. It will compile just fine but produce no executables. Which brings us back to needing a parser/resolver, which can parse the cargo metadata and look if a feature flag produced any executables.

Temporarily, I will try building with default first, check if at least 1 executable was produced, else build with all features: github.com/pkgforge-cargo/builder/commit/06bbb506…

Search Hashnode

Cross-Compiling 10,000+ Rust CLI Crates Statically

Responses(1)