[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: FOSDEM and beyond (next stable release of base)
From: |
Nicola Pero |
Subject: |
Re: FOSDEM and beyond (next stable release of base) |
Date: |
Thu, 11 Feb 2010 13:28:59 +0000 |
A common case, for example, is building many tools from the same
GNUmakefile - each of them created by compiling a file or two. We
don't parallelize building
the tools at the moment ....
I experimentally implemented this in trunk - for tools. Please give
it a go. You just need to use gnustep-make from trunk, then compile
using 'make -j N'
(where N is 2 or over, depending on how good your hardware is). :-)
Unfortunately, if you have different tools compiled in the same
GNUmakefile that share some source files (which seems to be common in
some projects), these
will break with the code currently in trunk (ie, the build will
occasionally fail). I'll implement a workaround later when I get some
more time. (if you're hit by this
before I implement a workaround, just avoid the '-j N' flags when
building - or read the release notes for more ideas of what you can do).
We'll delay 2.2.1 a little while this gets completed and tested - and
extended to other types of projects (apps, bundles, ctools,
frameworks, libs, test-apps, test-tools, etc).
WIth this change, 2.2.1 can build some projects much faster than 2.2.0
(eg, at work I have one where my build time went down from 98 seconds
to 57 seconds), but
keep in mind that 2.2.1 by default compiles with -O2, while 2.2.0
didn't, so most likely the average user will find that 2.2.1 compiles
slower just because
of -O2. If you don't want the -O2 flag, use 'make debug=yes'.
Thanks
Re: FOSDEM and beyond (next stable release of base), Quentin Mathé, 2010/02/09
Re: FOSDEM and beyond (next stable release of base), Riccardo Mottola, 2010/02/09