Hi Ronald + Carl,
We have been shipping PCH files for some time now, but I think you are
right that we have been very lucky that most of our clients haven't
hit compile problems until now. We will be making changes to our
product to regenerate PCH files on the target platform.
Thanks very much for the quick response guys and it's also pleasing to
see to see somebody from Microsoft replying!
Best regards,
Paul :)
[quoted text, click to view] "Ronald Laeremans [MSFT]" <ronaldl@online.microsoft.com> wrote in message news:<#P0R#2e5DHA.2580@TK2MSFTNGP11.phx.gbl>...
> DO NOT SHIP PCH FILES!!
>
> They are guaranteed to work only a single machine that has nothing change in
> the interim (hotfix, SP, whatever to the OS, the compiler, the CLR or
> anything else basically). They are simply a dump of memory at the time we
> have generated the info. Anything that changes that memory layout will make
> them incompatible.
>
> Ronald Laeremans
> Visual C++ team
>
> "Carl Daniel [VC++ MVP]" <cpdaniel_remove_this_and_nospam@mvps.org.nospam>
> wrote in message news:eERMoOc5DHA.2404@TK2MSFTNGP12.phx.gbl...
> > Paul wrote:
> > > Dear world,
> > >
> > > We are having issues with Windows 2000 SP4 and Pre-Compiled Header
> > > (PCH) files that have been previously compiled on Windows XP using
> > > .NET 2003. Recompiling the PCH files on Windows 2000 SP4 using /Yc
> > > does work, but we really want to ship one PCH file to our customers
> > > that will work on all versions of Windows.
> >
> > AFIAK, there's no guarantee that PCH files are portable off the machine
> > where they were created, regardless of OS vrersion. That you've been able
> > to do it at all is just luck. I'd like to be proven wrong about this -
> but
> > that's my understanding.
> >
> > -cd
> >
> >