Re: strange ORBit2 bugs ... & IDL distribution

"Gustavo J. A. M. Carneiro" <[email protected]>
Newsgroups gmane.comp.gnome.orbit.general,gmane.comp.gnome.components
Organization INESC Porto
Message-ID <[email protected]>
A Seg, 2003-05-05 às 14:50, Michael Meeks escreveu:
> Hi there,
> 
> 	Jpr just brought bug:
> 
> 	http://bugzilla.gnome.org/show_bug.cgi?id=101549
> 
> 	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)
> 
> dist-hook:
> 	for file in $(DONT_DIST_SOURCE) ; do \
> 	    rm -f $(distdir)/$$file ; \
> 	done
> 

  Michael, I think there is a cleaner way to accomplish the same thing,
with the nodist prefix. Example (from gnumexp):

# Numexp::Kernel and Numexp::Client interfaces
noinst_LIBRARIES=libnumexp_corba.a libgnumexp_shell.a
nodist_libnumexp_corba_a_SOURCES =		\
	Numexp_Kernel-common.c			\
	Numexp_Kernel-skels.c			\
	Numexp_Kernel-stubs.c			\
	Numexp_Kernel.h
nodist_libgnumexp_shell_a_SOURCES =		\
	GNumexp_Shell-common.c			\
	GNumexp_Shell-skels.c			\
	GNumexp_Shell-stubs.c			\
	GNumexp_Shell.h

CLEANFILES = $(nodist_libnumexp_corba_a_SOURCES) $(nodist_libgnumexp_shell_a_SOURCES)

  I hope this helps.

-- 
Gustavo João Alves Marques Carneiro
<[email protected]> <[email protected]>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.