internal compiler error with pch file after installing Windows SP2

R

rfroli

Hi,



After installing Windows SP2, I receive an internal compiler on a pch file
when trying to compile a C++ project on VS.Net 2003.

The pch file was built before the installation of SP2.



I can reproduce the same problem on any Windows XP by trying to reuse a pch
File built on Windows server 2003.



I found a post from Ronald Laeremans on a Microsoft private newsgroup where
he explains that "PCH files are a dump of the data segment of the compiler
process at the moment it creates the PCH." so any change to the compiler can
prevent it from reading back this data.

The post was concerning VS 2005. Is there the same behaviour in 2003?



We are shipping C++ libraries. The idea was to give our clients the pch file
instead of the include files (which are useless to our clients).



Is this possible or not recommended?



Any help would be appreciated.
 
B

Brandon Bray [MSFT]

rfroli said:
Is this possible or not recommended?

It's not recommended. PCH files are influenced by the machine configuration
as well. It's likely that PCH files built on one machine will have
unexpected behavior on another machine.

Hope that helps!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top