You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently discovered my C++ projects builds notably slower when using cargo-zigbuild, compared with a cmake toolchain I craft manually similar to https://github.com/mrexodia/zig-cross
After some debugging, I found that the initial process of fn execute_compiler (everything before actual zig Command::run) takes heavy amout of time, almost equal to the Command::run itself:
It would be great if the initial time could be reduced. Thanks!
The text was updated successfully, but these errors were encountered:
I guess most cost comes from spawning the Rust and Zig to checkout their versions. The versions could be checked when zigbuild is invoked and stored in zigcc-xx.sh.
I recently discovered my C++ projects builds notably slower when using cargo-zigbuild, compared with a cmake toolchain I craft manually similar to https://github.com/mrexodia/zig-cross
After some debugging, I found that the initial process of
fn execute_compiler
(everything before actual zigCommand::run
) takes heavy amout of time, almost equal to theCommand::run
itself:It would be great if the initial time could be reduced. Thanks!
The text was updated successfully, but these errors were encountered: