pch support

Casper Hornstrup ch at eudicon.com
Fri Jan 13 12:19:23 CST 2006


Just FYI here are some tests I made in November:

http://www.reactos.org/archives/public/ros-dev/2005-November/006273.html

Casper

-----Original Message-----
From: wine-devel-bounces at winehq.org [mailto:wine-devel-bounces at winehq.org]
On Behalf Of Steven Edwards
Sent: 13. januar 2006 17:01
To: Rolf Kalbermatter
Cc: wine-devel at winehq.org; Marcus Meissner
Subject: Re: pch support

Hi,

On 1/13/06, Rolf Kalbermatter <rolf.kalbermatter at citeng.com> wrote:
> This solution has been starting to form in my mind as well. It is even
> portable to MSVC it seems with a few small modifications to
winapi/msvcmaker.

I came up with a much more generic solution that will work on all
compilers and does not cause a dependancy issue. It requires some
minor code adjustments and there is a slight issue if you have errors
in linking. The error location is wrong so you need to have a way to
disable this if you have a real error to track the problem down, but
once I fixed ReactOS shell32.dll to use my hack my compile times on
gcc4 went from 30+ secs down to 9sec. MSVC went from 22 to less than 1
secound.

In short each module would have its own autogenerated master C file
that would include all of the others like the one I have attached.
Minus the #define hacks. I personally think its more of a nasty hack
but a configure switch could be added like

--enable-compilation-units

Because each header is only processed once, it give the same effect as PCH.


--
Steven Edwards - ReactOS and Wine developer

"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo




More information about the wine-devel mailing list