On Tuesday 15 July 2014 17:39:16 Milian Wolff wrote:
> OK, but why are PCH's enabled by default? The output of configure --help
> does not indicate that. I.e. why is -include .pch/Qt5Something even passed
> to GCC in the first place by default?
The output is wrong. It's been "auto" since the begin
On Tuesday 15 July 2014 08:15:55 Thiago Macieira wrote:
> On Tuesday 15 July 2014 15:32:10 Milian Wolff wrote:
> > It seems to be related to the number of jobs running, a "make -j1" seems
> > to
> > work most of the time, yet a "make -j40" on a compile cluster fails most
> > of
> > the time.
>
> T
On Tuesday 15 July 2014 15:32:10 Milian Wolff wrote:
> It seems to be related to the number of jobs running, a "make -j1" seems to
> work most of the time, yet a "make -j40" on a compile cluster fails most of
> the time.
Theories:
1) one of the compilation processes started before the PCH-creatio
On Tuesday 15 July 2014 15:32:10 Milian Wolff wrote:
> On Tuesday 27 May 2014 14:21:40 Thiago Macieira wrote:
> > Hello
> >
> > This is your friendly note that all Qt modules that don't have C or
> > assembly code are now using precompiled headers. I've tested this
> > solution for a couple of mon
On Tuesday 27 May 2014 14:21:40 Thiago Macieira wrote:
> Hello
>
> This is your friendly note that all Qt modules that don't have C or assembly
> code are now using precompiled headers. I've tested this solution for a
> couple of months with GCC on Linux, Clang on Linux, Clang on Mac and the
> Int
Hello
This is your friendly note that all Qt modules that don't have C or assembly
code are now using precompiled headers. I've tested this solution for a couple
of months with GCC on Linux, Clang on Linux, Clang on Mac and the Intel
compiler on Linux.
As it turns out, I didn't test it in all
