[omniORB] How to link to x86_win32 binaries with Borland C++b uilder?

[Thomas van der Ploeg]

The DLL's are microsoft DLL's.
I am not sure about how much name-mangling is standardized in c++ but I gave
up trying to link them.
It is however possible build everything after some 'minor' modifications
using C++ Builder.
Major changes are that you have to export inner classes explicitly, CBuilder
uses the standard io classes and some other
io functions work slightly different fom microsofts.
Other important point is that the omniorb sources and headers must be
processed using integer allignment for enumerators ( -b option I think ) and
the VCL libraries explicitly not.
It is not a simple switch but in this way I was able to compile and use
omniorb 2.5.0 and soon I hope to do the same thing with omniorb 2.6.1.

Regs,

Thomas.

> -----Original Message-----
> From:	Gregor [SMTP:gregorb@netvigator.com]
> Sent:	Wednesday, November 11, 1998 2:13 PM
> To:	omniorb-list@orl.co.uk
> Subject:	[omniORB] How to link to x86_win32 binaries with Borland
> C++builder?
> 
> I have been trying to get the omniORB examples working with C++Builder 3.0
> from the IDE.  I can get the source compiling OK, i.e. eg1, but have
> complete failure when linking to the DLL's in the distribution.
> 
> I have searched the Borland and omniORB FAQ's but what I found didn't seem
> to provide the answer.  I have created borland .lib files and tried
> turning
> underscores off but nothing seems to get me even close to linking to these
> DLL's.
> 
> I presume there is a simple "switch" that sorts this out somewhere so I am
> hoping that someone on this list has done this with BCB and can help.
> 
> 
> Thanks
> Gregor Bruce
>