A full debug build from scratch (with sanitizers and static analysis turned off) of one of my games (including my homemade engine) takes about 1.8s on my 6 years old i7-8565U - measured with `time ninja`. That's about 10k lines of code.
It goes up to 6s when I enable ImGui integration, as ImGui is written in C++.
When I build it with an embedded copy of entire Allegro 5 library, it goes up to 13s.
A fully optimized complete build including both ImGui and Allegro takes 25s. cloc reports 325k lines of code.
During development, most of the time you just compile one unit incrementally, which boils it down to milliseconds either way, so that's probably the figure that's most relevant to your question (although clang-tidy can push it back to a few seconds).
Comments
A full debug build from scratch (with sanitizers and static analysis turned off) of one of my games (including my homemade engine) takes about 1.8s on my 6 years old i7-8565U - measured with `time ninja`. That's about 10k lines of code.
It goes up to 6s when I enable ImGui integration, as ImGui is written in C++.
When I build it with an embedded copy of entire Allegro 5 library, it goes up to 13s.
A fully optimized complete build including both ImGui and Allegro takes 25s. cloc reports 325k lines of code.
During development, most of the time you just compile one unit incrementally, which boils it down to milliseconds either way, so that's probably the figure that's most relevant to your question (although clang-tidy can push it back to a few seconds).