[omniORB] omniorb configure / build issues

[Stefan Seefeld]

hi (Duncan),

I'v been trying to add an 'omniorb-config' script that
could be used to report all the important flags I have
to know when developing with omniorb. Notably, the docs
list flags per platform that I have to define before
including omniorb headers.
Now that you have an autoconf based build system, i.e.
one with an automatically gernerated config file, why
can't you put these flags right into that config file ?

Right now a typical compile command looks:

g++ -c -fPIC -O2 -Wall -Wno-unused -fexceptions -I.. -I./.. -I../../../../include/omniORB4/internal 
-I../../../../include/omniORB4/internal -D_REENTRANT -DUSE_omniORB_logStream -D_OMNIORB_LIBRARY 
-DCONFIG_DEFAULT_LOCATION='"/etc/omniORB.cfg"' -DCONFIG_ENV='"OMNIORB_CONFIG"' -DUnixArchitecture 
-I. -I. -I../../../../include -I../../../../include -D__OSVERSION__=2 -D__linux__ -D__x86__  -o 
shared/proxyFactory.o proxyFactory.cc

the __OSVERSION__, __linux__, and __x86__ variables could
equally well be put into omniORB4/acconfig.h, so not only
would your own compile commands look slightly more readable,
but you wouldn't need to require as much work from the
users of your code. (as this header would be included
implicitely wherever omniORB4/CORBA.h is included)

Regards,
		Stefan