On 14/02/12 13:30, Mark Wielaard wrote:
Hi,
Added Tom to the CC, see thread here:
http://thread.gmane.org/gmane.comp.documentfoundation.libreoffice.devel/24055/focus=24096
(Although it seems posts from non-subscribers, aka me, are not allowed,
so you won't see my earlier reply there. I'll
On 14/02/12 11:52, Michael Meeks wrote:
Hi Michael,
On Mon, 2012-02-13 at 16:06 +0100, Michael Stahl wrote:
(of course i don't care if you do it for a special merged libs mode,
but C++ development is already a sufficiently unproductive activity that
we shouldn't make it even more so...)
Hi Michael,
On Tue, 2012-02-14 at 13:07 +0100, Michael Stahl wrote:
the problem is more likely that in tail_build we first compile all the
object files, and only after they have all been built they are linked
into libraries/executables.
Perhaps; could it also be that we like to
Hi,
Added Tom to the CC, see thread here:
http://thread.gmane.org/gmane.comp.documentfoundation.libreoffice.devel/24055/focus=24096
(Although it seems posts from non-subscribers, aka me, are not allowed,
so you won't see my earlier reply there. I'll send it to you separately.)
On Tue, Feb 14,
On 2012-02-14 14:22, Michael Meeks wrote:
Perhaps; could it also be that we like to compile with gcc in some
eight way parallel way, but when it comes to linking, we -really-
don't want to bog our machine down in that way ? I wonder if we could
explicitly limit parallelism of linking in some
On 14/02/12 13:30, Noel Grandin wrote:
On 2012-02-14 14:22, Michael Meeks wrote:
Perhaps; could it also be that we like to compile with gcc in some
eight way parallel way, but when it comes to linking, we -really-
don't want to bog our machine down in that way ? I wonder if we could
On 2012-02-14 15:49, Michael Stahl wrote:
do we _really_ invoke javac once for each source file anywhere? at
least in gbuild it's invoked once per jar file (technically, per
JavaClassSet that the jar depends upon), which is the only sane way to
do it.
You are correct sir.
But I think I saw
