From: Raja R Harinath <[EMAIL PROTECTED]> > > However, it appears that the reason you want to build $(libglib) is > that you want to distribute the built sources. It's not necessary to > distribute those files which are generated using C code (i.e. using > glib-genmarshal.*). It is only necessary to distribute stuff built > with Perl. > > Wouldn't that be a better way to solve the problem rather than > building $(libglib)? Of course, this'll require the use of > BUILT_SOURCES with a sane released 'automake' (say v1.5). > > BUILT_SOURCES = $(perl_built_files) $(c_built_files) > dist-hook-local: $(perl_built_sources)
Is this the canonical way of avoiding including the marshaller code in a tarball? Something like BUILT_SOURCES = foo_marshal.c foo_marshal.h I'm not familiar with this automake option, so I'd appreciate it if you could point me some where I could get some more discussion. I don't remember seeing it in the online version of the book, but I could be wrong. Since this seems to be going off-topic for gtk-devel-list, I'm setting it to go to gtk-list instead. Ron Steinke _______________________________________________ gtk-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/gtk-list