---
title: "Ajam (@azathothas) | Hashnode"
description: "Ajam (@azathothas) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@azathothas"
---

@azathothas

# Ajam

@azathothas · Nepal · Joined October 2023

[Website](https://linktr.ee/Azathothas)

## Comments

[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: https://github.com/pkgforge-cargo/builder/commit/06bbb506e123ae7d2a1d9fdd8d459131a596b350](https://hashnode.com/posts/cross-compiling-10000-rust-cli-crates-statically/685d476a73349620fb4000c9/comment/6866fb8628dcb56e814790ef#reply-686caf563dc698775dfd2cb3)

Reply · Article · Jul 8, 2025 · [Cross-Compiling 10,000+ Rust CLI Crates Statically](https://hashnode.com/posts/cross-compiling-10000-rust-cli-crates-statically/685d476a73349620fb4000c9)

[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.](https://hashnode.com/posts/cross-compiling-10000-rust-cli-crates-statically/685d476a73349620fb4000c9/comment/6866fb8628dcb56e814790ef#reply-6867912480d9d41adaf8bdbf)

Reply · Article · Jul 4, 2025 · [Cross-Compiling 10,000+ Rust CLI Crates Statically](https://hashnode.com/posts/cross-compiling-10000-rust-cli-crates-statically/685d476a73349620fb4000c9)
