Quote Originally Posted by Uwe View Post
What a rocket - on my system it takes several minutes to build the Qwt library from scratch.
That's an i7-2600 (4 cores, 8 HT-threads), a debug build with gcc on x86-64 linux. The optimized build takes about twice that time.

I just did a quick benchmark:
make -j1: 34 sec.
make -j1 + unity: 7 sec.
make -j9: 8.3 sec.
make -j9 + unity: 4 sec.

(Note: -j9 seems to be the optimal value for this CPU).
The less cores/HT-threads you have, the more the speed benefit of a unity build. On an infinite-core machine I guess the ordinary build would approach the unity one, but until then...

Anyway I don't promise anything, but at least now I have this scenario in mind. Also using the same name for different functions ( even if static to specific files ) is an accident - nothing I would call good practice. Guess most IDEs ( if I would use one ) would have problems with such a thing.
Good enough for me!

PS: in trunk the 2 qwtRenderBackground functions have been moved to QwtPainter::drawBackground
Thanks, I just saw that in SVN.

Take care,
Alexander