[orbitcpp-list] Targetting orbitcpp at ORBit 0.5

[Phil D. <ph...@us...>]

Hi All,

Just a mail to prevent duplication of effort:

It seems like people are having all sorts of strife trying to work
with multiple (unsupported) versions of ORBit.  To fix this, I'm
currently porting orbitcpp to work with the 'stable' ORBit-0.5.X
releases. I've attached a patch which allows cvs orbitcpp to compile
against ORBit-0.5.6.

Note that the following things are broken in ORBit-0.5.6:

   - Array memory management (Segfaults on CORBA_free)
   - CORBA_Any (the ORBit compiler generates code for complex types
   which doesn't compile)

Everything else seems to work (according to the orbitcpp 'everything'
test harness), so this should be okay for people who don't need these
features (I've probably temporarily broken the orbitcpp any support
with this patch in any case). I'm currently working on patches to
ORBit-0.5 to fix the above problems.

I was thinking that it is probably best to target orbitcpp HEAD at 0.5
for the time being (since Elliot has 'officially' disowned ORBit CVS
HEAD), and create a archive branch to orbitcpp for ORBit-2. Does this
sound like a sane idea?

Merry Christmas all,

Cheers,

Phil