[omniORB] Compilation Speed

[Brenneis, Steven W.]

It would be inappropriate to include the IDL-generated *.hh files in your precompiled header for the reasons you have already
mentioned plus the problem VC has with noticing certain changes to class defintions which change the virtual function table.
However, it can be helpful to include files like omnithread.h and others.  Because of header guarding and the way VC parses
precompiled headers, these omniORB system headers, which appear repeatedly in IDL generated stubs, will already have been *seen* by
the compiler and it can help your compile time.

P.S. Sorry about the MS quoting format.  My company seems to like playing musical E-Mail servers.

> -----Original Message-----
> From:	jon.kristensen@kongsberg-simrad.com [SMTP:jon.kristensen@kongsberg-simrad.com]
> Sent:	Friday, August 20, 1999 6:36 AM
> To:	Sai-Lai Lo
> Cc:	omniorb-list@uk.research.att.com
> Subject:	Re: [omniORB] gcc 2.95 compiler warning
> 
> 
> 
> A short note on compilation speed:
> 
> I'm using Visual C++ 6.0, and have been investigating use of precompiled
> headers. The reason for this that for large projects in which the source is
> organized into a large number of "small" files, 90% of the compilation time is
> used to process omniORB or win32 header files.
> 
> It seems to me that precompiled headers is not practical on omniIDL generated
> code and any file that includes omniIDL generated headers. The main obstacle is
> that to effectively use precompiled headers, you need a relatively stable set of
> header files that are included AT THE TOP of each source file. The omniORB
> ..SK.cpp files inclues the corresponding header files which in turn includes the
> omniORB headers. This violates the rule mentioned.
> 
> Is this an issue on other platforms/compilers?
> 
> Btw, is there any information available regarding the release date of v2.8.0?
> 
> Best regards,
> Jon Kristensen
> Kongsberg Simrad AS, Horten, Norway
> phone:    +47 33 03 43 62
> fax: +47 33 04 76 19
> email:    jon.kristensen@kongsberg-simrad.com
> 
>