[omniORB] optional support for autoconf

[Stefan Seefeld]

I'm in the process of rewriting the build system for the berlin 
project. It's autoconf based. Among other things, autoconf performs 
a specified set of platform/ build environment checks, and sets 
variables and compile time flags (-D macros) accordingly. To use 
these macros, there are two possibilities:

* include them into the makefile, such that they can be used in
  the command line which invokes the compiler

* create a special configuration header which lists them all. In
  this case, a special macro -DHAVE_CONFIG_H is defined.

As the list of macros becomes large, it appears reasonable to
use the second option, where the compile command can be kept
readable, and all the flags are passed by means of a special header.

I'd like to propose that omniidl generated sources support this
feature, i.e. that it is possible to include a header file, which
is provided by the user. I'v noticed that such a technique is already 
used internally by the COS skeleton files. Whenever people use omniORB 
in a project that is built by means of autoconf, that would greatly 
facilitate the work. All the system dependent flags (_x86_, etc.) could
be kept there...

Regards,	Stefan
_______________________________________________________              
              
Stefan Seefeld
Departement de Physique
Universite de Montreal
email: seefelds@magellan.umontreal.ca

_______________________________________________________

      ...ich hab' noch einen Koffer in Berlin...