3 ms·

I just cloned the Starship repo and cargo --release built it and it took six minutes and 30 seconds (which did feel interminable). The author says it takes him

I just cloned the Starship repo and cargo --release built it and it took six minutes and 30 seconds (which did feel interminable). The author says it takes him 15 minutes "for building just the main.rs", 10 minutes for "lib.rs" and an unspecified time for "everything else". My CPU is from 2012. What on earth is he doing this on, a TI-83? Or am I missing some intricacy of whatever Gentoo is doing that would inherently inflate build times by an order of magnitude?

nindalf 2y ago
Just another data point. I cloned and ran `cargo build --release`. It took 2 mins and 2 seconds (M1 Pro, 2021). Just want to say, creating a release build is really unusual! You'd do that relatively rarely. Most of the time you'd create a debug build, which took 29.56 seconds on my machine for a clean build and 1.45 seconds for an incremental build with one line changed. I sympathise with the author's running on underpowered hardware, but it might not reflect the experience of the average Rust developer.
rascul 2y ago
5m 39s here on a 2017 CPU: Intel(R) Pentium(R) CPU G4560T @ 2.90GHz
timw4mail 2y ago
Rust doesn't play quite as nicely with Gentoo's packaging system as C/C++, but yes, that seems excessively long. Then again, I'm fairly sure I have starship installed via `cargo install`, not via portage (Gentoo's packaging system). I'm a Rust and Gentoo lover :D
saati 2y ago
> The author says it takes him 15 minutes "for building just the main.rs", 10 minutes for "lib.rs" and an unspecified time for "everything else". That's weird, cargo displays the current crates under compilation, not files as that's not the compilation unit in Rust, the author seems to be fibbing.
- TheDong 2y ago
  $ emerge -v starship <...> Running `rustc --crate-name starship --edition=2021 src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib <etc> Running `rustc --crate-name starship --edition=2021 src/main.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin <etc> This person is using gentoo, gentoo does print it like that.

nindalf 2y ago

Just another data point. I cloned and ran `cargo build --release`. It took 2 mins and 2 seconds (M1 Pro, 2021). Just want to say, creating a release build is really unusual! You'd do that relatively rarely. Most of the time you'd create a debug build, which took 29.56 seconds on my machine for a clean build and 1.45 seconds for an incremental build with one line changed. I sympathise with the author's running on underpowered hardware, but it might not reflect the experience of the average Rust developer.

rascul 2y ago

5m 39s here on a 2017 CPU: Intel(R) Pentium(R) CPU G4560T @ 2.90GHz

timw4mail 2y ago

Rust doesn't play quite as nicely with Gentoo's packaging system as C/C++, but yes, that seems excessively long. Then again, I'm fairly sure I have starship installed via `cargo install`, not via portage (Gentoo's packaging system). I'm a Rust and Gentoo lover :D

saati 2y ago

> The author says it takes him 15 minutes "for building just the main.rs", 10 minutes for "lib.rs" and an unspecified time for "everything else". That's weird, cargo displays the current crates under compilation, not files as that's not the compilation unit in Rust, the author seems to be fibbing.

TheDong 2y ago
$ emerge -v starship <...> Running `rustc --crate-name starship --edition=2021 src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib <etc> Running `rustc --crate-name starship --edition=2021 src/main.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin <etc> This person is using gentoo, gentoo does print it like that.