strange ORBit2 bugs ... & IDL distribution
- From: Michael Meeks <michael ximian com>
- To: orbit <orbit-list gnome org>
- Cc: bonobo <gnome-components-list gnome org>,JP Rosevear <jpr helixcode com>, Jaka Mocnik <jaka gnu org>,Bill Haneman <bill haneman sun com>
- Subject: strange ORBit2 bugs ... & IDL distribution
- Date: 05 May 2003 14:50:31 +0100
Jpr just brought bug:
to my attention; this is caused by a rather nasty backwards
compatibility issue; The root problem is that if you generate
stubs/skels on a new machine, and then ship them to an old machine, they
don't work against the older ORB on that machine.
Ie. we remain fully backwards compatible at all times; however we can't
be forwards compatible always; thus if you build '2.6' stubs and run
them against a '2.4' ORB you get problems. The reverse is never true -
it's always safe to run '2.4' stubs against '2.6', '2.8' ... ORB.
Unfortunately, autotools makes it very easy to ship auto-generated
code; in fact you have to work hard to stop it; thus, if anyone is
building IDL in their project I recommend that you use:
DONT_DIST_SOURCE = $(CORBA_SOURCE) $(marshal_sources)
for file in $(DONT_DIST_SOURCE) ; do \
rm -f $(distdir)/$$file ; \
Which can be used to delete your glib-genmarshal created stuff, and any
IDL stubs/skels/common (cf. libbonobo/bonobo/Makefile.am).
That will ensure your project is fully backwards compatible, and that
targets generated on old machines will still run perfectly.
firstname.lastname@example.org <><, Pseudo Engineer, itinerant idiot
] [Thread Prev