100k loc without a reasonable architecture is… problematic.
I have run into problems with C++ linker/optimizers which will choke on big (50k loc) .cpp files which are auto-generated from definitions, they get slow like that, build times around 20 minutes for the worst of them. Keep the files more like 10k loc and down if you don’t want this kind of issue.
Nowhere did I say there’s no reasonable architecture. Please don’t put words in my mouth. What I said, is that I haven’t found a good way to get quick compiles end to end. And already I don’t have any files more than 3-4k loc, most are under 1k.
Yeah I doubt it. I’ve worked in large Rust codebases too. I’d do some benchmarking. Cargo has some nice flags that let you see exactly what it’s doing. You can open the compilation report up in a browser and zoom in on different steps of the process and see everything.
No, I’m not using --release every time of course. And sometimes it’s minutes even with the cache.
That’s highly abnormal to have minute long debug build times.
for 100k loc?
100k loc without a reasonable architecture is… problematic.
I have run into problems with C++ linker/optimizers which will choke on big (50k loc) .cpp files which are auto-generated from definitions, they get slow like that, build times around 20 minutes for the worst of them. Keep the files more like 10k loc and down if you don’t want this kind of issue.
Nowhere did I say there’s no reasonable architecture. Please don’t put words in my mouth. What I said, is that I haven’t found a good way to get quick compiles end to end. And already I don’t have any files more than 3-4k loc, most are under 1k.
Yeah I doubt it. I’ve worked in large Rust codebases too. I’d do some benchmarking. Cargo has some nice flags that let you see exactly what it’s doing. You can open the compilation report up in a browser and zoom in on different steps of the process and see everything.
I’ve tried looking before and couldn’t get a significant improvement. I’ll have to investigate it again I guess.