Building kdelibs (1/6)
Preparing build system for kdelibs.
Running cmake...
Compiling, attempt 1...
Build succeeded after 44 minutes, and 56 seconds.
Installing kdelibs.
Overall time for kdelibs was 48 minutes, and 49 seconds.
Building kdepimlibs (2/6)
Preparing build system for kdepimlibs.
Running cmake...
Compiling, attempt 1...
Build succeeded after 7 minutes, and 53 seconds.
Installing kdepimlibs.
Overall time for kdepimlibs was 8 minutes, and 14 seconds.
Building kdebase (3/6)
Preparing build system for kdebase.
Running cmake...
Compiling, attempt 1...
Build succeeded after 52 minutes, and 35 seconds.
Installing kdebase.
Overall time for kdebase was 57 minutes, and 44 seconds.
Building kdesdk (4/6) # note: several subdirs commented out
Preparing build system for kdesdk.
Running cmake...
Compiling, attempt 1...
Build succeeded after 8 minutes, and 26 seconds.
Installing kdesdk.
Overall time for kdesdk was 8 minutes, and 45 seconds.
Building kdeplasma-addons (5/6)
Preparing build system for kdeplasma-addons.
Running cmake...
Compiling, attempt 1...
Build succeeded after 6 minutes, and 15 seconds.
Installing kdeplasma-addons.
Overall time for kdeplasma-addons was 6 minutes, and 24 seconds.
Building plasma (6/6) # this is: playground/base/plasma
Preparing build system for plasma.
Running cmake...
Compiling, attempt 1...
Build succeeded after 3 minutes, and 25 seconds.
Installing plasma.
Overall time for plasma was 3 minutes, and 35 seconds.
Friday, January 09, 2009
Compile Time
Recompiling kdelibs, kdepimlibs, kdebase, kdesdk, kdeplasma-addons, playground/base/plasma all in all takes about 2h 13min on my t41p (1.7GHz, 1.5GB ram). It's still quite fast imo, but I imagine with today's hardware it's maybe 30 minutes? See below for detailed infos. I'm using mpyne's excellent kdesvn-build scripts to build KDE from trunk. I even believe this should be the default way for building trunk instead of the rough road we propose on techbase right now. Are there any reasons not to use kdesvn-build?
Subscribe to:
Post Comments (Atom)
6 comments:
I use kde-svn every day to build most of kde in my machine its very fast specily using icecream :).
yeah, i defiantly agree with using kdesvn-build instead of the current way
I was just today planning to start using trunk version from KDE to test bugs and reporting...
But... (there is always a but) I went to page and then there was these informations for what is located and where and how you should have SVN as name or if you are anonymius you should be like on the other doc and use CVS and for example to SVN usage etc... few minutes later I made my mind and planned to stay on Mandriva's cooker version and suffer from it's small sloweness (currently KDE is broken (4.1.86 version) because X11-server has problems with ATI and NVIDIA drivers...
Now when I saw this, I tought I would give a new change for the idea to start assisting KDE development as bug-hunter...
2h time is not big deal for me... I could easily recompile that 1-2 times a day but if it is possible to get lower... I am more than just a ear to hear that...
Reading this I get the impresstion that I have to blog about how I compile KDE with kdesvn-build :-)
Once this is setup correctly and all dependencies required for compilation are met, compiling is *really* simple.
The compilication itself is not so dificult... just the setup in the first time and to know what to do to where.
Example:
1. depencies
2. what parts needed for good testing
3. how to start KDE
(4. change to make compilication faster on next time when code is only little changed?)
@Fri13: The dependencies are available on the techbase page.
Once you compiled successfully with kdesvn-build, you can simply do a `svn up` and then in the build directory `make && make install`.
Post a Comment