Hacker News Reader

Maybe a dumb question but how would I go about using it with rust(c) and cargo? Would love to try it out, if it decreases total compile times.

View on HN

RUSTFLAGS="-C linker=clang -C link-arg=-fuse-ld=/path/to/mold" cargo build

or persitant in your project:

.cargo/config.toml

[target.x86_64-unknown-linux-gnu] linker = "clang" rustflags = ["-C", "link-arg=-fuse-ld=/PATH/TO/mold"]

-fuse-ld has been replaced by --ld-path in clang 12+

Good to know, thanks.

fuse-ld still works though.

I wonder -- "-fuse-ld" has some somewhat surprising behavior in how clang ends up discovering the linker. I think that even if clang has a sibling `lld` in the same distribution, "-fuse-ld=lld" will pick "ld.lld" from the $PATH if it's present in there before the directory where clang and lld are installed.

So maybe that "--ld-path" option helps resolve ambiguity by expecting an explicit path instead of a linker name.

Thank you. Will try it later

"mold -run cargo build" would also work.

Warning: don't do this if you use rust-analyzer or any other IDE that uses cargo check.

The flags are part of the cache hash, so your IDE and cli constantly invalidate the cache and compile from scratch.

Reply on news.ycombinator.com