4 ms·
I've worked on code that took that long to compile, and the cause of the problem was usually bad recursive makefiles doing work over and over again. At the oth
by btilly 9y ago
I've worked on code that took that long to compile, and the cause of the problem was usually bad recursive makefiles doing work over and over again.
At the other extreme I've also worked at Google and have seen insanely complex C++ code bases compile in 30 seconds flat.
Multiple hour build times usually show that nobody smart enough had the interest and authority to solve the problem properly. It doesn't generally mean that your project is awesome. It certainly isn't something that I would brag about.
- InclinedPlane 9y agoOK, that's great for google, but "complex" doesn't necessarily mean much. Do you think the linux kernel devs are slouches? The gcc devs? Both of those projects take hours to compile on reasonable hardware, and that's not for lack of trying. Also, sometimes it's not about code, it's about digital assets, which is going to be IO bound. I've worked on projects that took a full working day to do a clean compile and others where it was necessary to do binary integrations instead of code because the overall build time would otherwise be measured in days or weeks.