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

[David Morgenlender]

Thomas,

>I think I encountered only two true compiler bugs.
>One is the need for the -b switch for CBuilder to compile omniorb code, =
it
>should not have been necessary, certainly not because VCL does not work =
with
>-b switch on.

That sounds familiar.  I may have used that as a workaround, but I'm not
positive.

>The other is that the precompiled headers often get funny but it is easy=
 to
>switch that off.

I think I sometimes got strange compiler errors that went away if I did a=
 full
build, perhaps due to precompiled headers.

>I must say that I made it a habit to keep omni and VCL code as separated=
 as
>possible and may have and think I have avoided a lot of problems in that
>way.

As I recall, I couldn't get omniORB to build correctly by itself.  So I =
never
got as far as trying to integrate it into my app.

>At the moment I am not completely happy about how I did set up the =
project
>for CBuilder, it is not completely consistend with the original omniorb
>project ( naming of libs and such ).
>
>But, yes I did get it running and it still runs fine for my purposes, =
though
>I must admit I never tried a complete test for all functionality.
>In fact I thought that at last I had found a commercial compiler that =
has
>namespaces implemented correctly.

I don't understand why you didn't run into the other compiler bugs I ran =
into.
IAE, congratulations & good luck with it!

=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