Darren Freeman <[EMAIL PROTECTED]> writes:
> Don't forget that it only uses the pre-compiled header for the first
> #include. To get the benefits you still have to include all the project
> includes from one header. Lyx isn't doing this, right?
Look at things like src/pch.h.
JMarc
On Fri, 2007-09-07 at 09:25 +0100, José Matos wrote:
> On Friday 07 September 2007 08:25:30 Darren Freeman wrote:
> > Check out gcc's new precompiled header functionality.
> > http://gcc.gnu.org/onlinedocs/gcc/Precompiled-Headers.html
> >
> > Basically gcc-3.4 and newer allow you to dump the state
On Friday 07 September 2007 08:25:30 Darren Freeman wrote:
> Check out gcc's new precompiled header functionality.
> http://gcc.gnu.org/onlinedocs/gcc/Precompiled-Headers.html
>
> Basically gcc-3.4 and newer allow you to dump the state of the compiler
> to disc after your headers are compiled, and
Darren Freeman <[EMAIL PROTECTED]> writes:
> On Thu, 2007-09-06 at 18:51 +0100, José Matos wrote:
>> I am not reticent. I am still compiling. :-(
>>
>> That is why I like André's goal to reduce the compile time. Does anyone
>> has
>> some simple step by step procedure to make ccache (or any
stency, but lets
face it the reason for not including something is usually to speed up
compilation in the first place.
I remember Andrew Tridgell (Samba) giving us a talk on it just after
another person demoed distcc, a distributed gcc. By using precompiled
headers, Tridge was able to compile S
