4 ms·
Back when I compiled on a cray I had problems with make because files could compile within a second so make would want to recompile them. I use a lot of C++ te
by gumby 6y ago
Back when I compiled on a cray I had problems with make because files could compile within a second so make would want to recompile them.
I use a lot of C++ templating so these days fast builds are just a fantasy no matter what I do. Unlike the author I rely on incremental builds for development but do a full build before pushing
- algo_trader 6y agoc++ templates are a real killer. Have u tried a cloud compiler? Did your company ever try a build server ?
- gambiting 6y agoI work in video games, large AAA game with absolutely crazy amount of templating, the compilation time is about 10-15 minutes, and that's with Fastbuild and hundreds of workstations participating in the build process. Once it's built it's a bit quicker, about 60 seconds from pressing build to the game starting, the linking is killer, it takes soo long every time.
- pjmlp 6y agoNo use of external templates or having common subset in a binary library and then use private inheritance?
- gumby 6y agoThere are a lot of techniques to help, but they only help so much. I could opt for less metasyntactic power but it would make the code less expressive, harder to follow, and more error prone. The tradeoff is worth it. Given I used to compile on a .25 MIPS KA-10 there's little to complain about. For a while in the mid 80s I had two symbolics lispm consoles in my office because I would use one as a build machine and one for development and other stuff (one had a gasp color display attached as well!). That was when programmer time was worth the capital cost. Honestly it didn't matter as much as incremental development was done with interpreted code anyway. But time spent compiling is time spent reflecting, and doesn't have to cost you flow.