[omniORB] AIX

[Craig Rodrigues]

On Mon, Nov 29, 1999 at 10:33:54AM -0500, Gary D. Duzan wrote:
> compiler of the xlC/C Set++ variety, which should work. To use the
> gui version, however, would be more work. Rumor has it that the
> more advanced gui version will get a real command line interface in
> the future, which would simplify things.

If you want the full story about IBM C++ compilers, here it is.

Currently, VisualAge C++ (VAC++) version 4.0 only comes
in a GUI based version.  There is a script called vacbld which
can be run from the command-line, but it is a pain in the ****
because it does not use standard Makefiles (you need to use special
VAC++ specific project files), and does not take any of the old
command-line flags to xlC. 

On a separate CD with VAC++, there is something called 
"IBM C and C++ Compilers, version 3.6.4".  This is internally called
"Portapak" by IBM, because it is basically the old compiler back-end
and front-end, ie. xlC, xlc, cc, etc.  Omniorb has been compiled
with this version of the xlC compiler (version 3.6.6 is the latest).

The only problem is, the xlC compiler backend is not the same as the
VAC++ backend.  VAC++ is an ISO C++ compliant compiler, while xlC is
not.

According to my contact in the IBM compiler group, a lot of customers
have been complaining about VAC++ not including the old xlC command-line
interface.  So, in about the middle of 2000, VAC++ 4.1 should be out
which will be one unified ISO C++ compiler with GUI-interface, xlC interface,
incremental compiler, etc. all working and singing together.

So that's the long answer.  The short answer is, if you have VAC++,
look for the other CD which has xlC, install that, and build omniORB
with xlC 3.6.x.

IBM makes it so hard to write software for them, it's amazing that
anyone does. :)
-- 
Craig Rodrigues        
http://www.gis.net/~craigr    
rodrigc@mediaone.net