Welcome to software development. :-) Seriously, I probably spend at least 10% of my time dealing with broken libraries, badly documented build processes, and other depressing obstacles.
If you can get past these kinds of problems—and more importantly, if you submit fixes to spare the next person the pain—then you'll make a great developer.
Sounds like a good idea to me, esp. for people working on a laptop.
Seriously, do you have to compile the whole program for every code change? I suspect that is not necessary?
Also a common way to speed up build times is to build in release mode.
Core i7, 12GB of RAM, 10k RPM HDDs.
The built executable worked first time too, which was impressive for a project of that size, given that it was the very latest bleeding edge trunk source code.
For comparison, I tried to build Mozilla three or four years ago, and gave up. The Chrome build environment setup instructions, while long and tedious (especially on Windows), are excellent.
This serves as a nice textbook example of why implementing things like menus and keyboard shortcuts by hardcoding keycodes in C++ is a horrible idea.