On 26-1-2014 22:07, Martin Owens wrote:
On Sun, 2014-01-26 at 21:08 +0100, Johan Engelen wrote:
- I really hope we can set all defaults correctly on Windows, so we
can build from a new checkout with the same amount of effort as we do now (almost zero).
With autotools? Even on Ubuntu, with apt-get build-deps and easy to aquire bzr, it's more difficult than I was expecting.
On Windows, from scratch, it is: - bzr checkout devlibs somewhere - bzr checkout lp:inkscape somewhere-else - fix up mingwenv.bat if you want (easy to see all "options" to get started in one file) - g++ buildtool.cpp -fopenmp -O3 -o btool.exe - btool -j - done
For a new branch if you already have a main branch: - bzr checkout branch somewhere - copy mingwenv.bat and btool.exe from your main branch - btool -j - done
No configuration parameters are needed to get started. The build is done out-of-source automatically, and the built binaries will be "installed" into ./build/inkscape folder. Pretty simple and IMO very convenient. I very much want to preserve this build-"complexity" on Windows.
I wanted to test the build times between my machine Celeron toshiba vs my wife's new i7 System76 laptop. 4.5 hours vs 55 minutes. So, it's certainly faster to build than it used to be, although I guess the bulk of the time isn't make or autotools, but gcc.
55 mins on an i7 means that you are not doing a parallel build. Try build -j (btool has to be built with -fopenmp), or make -j 20. (some random number above the number of cores that you have, > cores+2 or smth will do, btool -j does 20 by default). The laptop should feel slow when it is compiling, and your battery should drain fast :) Just tried again: clean build takes my i7 @ 3.4 GHz a little over 6 minutes. (because of running more threads in parallel than the amount of cores, the threads no longer wait for file loading, explaining why RAM-disk or SSD did not seem to bring anything).
Cheers, Johan