[omniORB] How to link to x86_win32 binaries with Borland C++builder?
David Morgenlender
dmorgen@alum.mit.edu
Wed, 11 Nov 1998 14:49:29 GMT
Gregor,
>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.
I tried getting omniORB working under BCB3 awhile back. I ran into one =
problem
after another ... compiler bugs ... work around one, then the next one =
popped
up. Borland tech support confirmed all but one of my reported bugs as =
bugs;
the one they didn't confirm they said they could not repeat. I haven't =
gotten
back to them on this one yet.
The bad news ... I never got it working, after spending a lot of time on =
it.
The client changed project specs which led to my being able to avoid =
needing
CORBA for the BCB3 app. The good news ... I'm now using omniORB quite
successfully. Basically, the architecture was to have a CORBA server =
running
under ETS-Kernel (a realtime OS); the BCB3 app would be the CORBA =
client,
running under NT. The client then said they needed to be able to write =
Q&D apps
in Visual Basic; at least back then, there were no good CORBA solutions =
for VB,
but COM was built in. So I wrote a "mediator" to run under NT; this is =
a COM
server & CORBA client; apps talk to it via COM; it translates the calls=
to
CORBA to communicate with the ETS app. Writing VB apps to deal with this=
COM
interface is easy. Likewise, it's fairly easy to use BCB3 to act as a =
COM
client ... actually, the coding is easy ... but figuring out how was a =
real bear
... the documentation is either awful or non-existent!
So, I've got things working. Unfortunately, it doesn't help you with =
your
problem!
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
Dave Morgenlender
e-mail: dmorgen@alum.mit.edu
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D