please make it easier to hack on frameworks

[Oswald Buddenhagen]

On Sun, May 05, 2013 at 11:47:04AM +0200, Alexander Neundorf wrote:
> Ok, so what is the right way to get Qt properly rebuilt ?
> 
mv $builddir/config.status $safeplace
rm -rf $builddir/*
mv $safeplace $builddir/config.status
cd $builddir
./config.status
make

works also for a top-level build, except that you should keep the
top-level Makefile (as the qtbase config.status doesn't re-create it).

a no-op rebuild on my work machine this takes < 5 min for qtbase, and <
15 min for all of qt (the bulk being linking webkit).

export CCACHE_HARDLINK=1 is recommended for maximum speed and reduced
disk usage.
i also use CCACHE_UNIFY=1, but that doesn't help when compiling with
debug info. it doesn't help much for qt anyway, but is a potentially big
win for kde (because the apidox are in headers).

i use the attached wrapper program to get ccache and icecream into the
build process.

i also use that for compiling kde - cmake isn't smart enough to track
dependencies of configure tests, so when i update after several weeks
(or even months nowadays) i regularly get configure-related breakages
that go away with a clean builddir. having the first attempt cached
sometimes goes a long way. and ccache is cool for testing patches anyway
(apply => revert => no-op rebuild).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wrapcc3.c
Type: text/x-csrc
Size: 7275 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20130505/7d7f29f1/attachment-0001.c>