Hey Boris, On 14/03/2008, Boris Kolpackov <[EMAIL PROTECTED]> wrote:
> You can write normal Makefile rules in Makefile.am. You can use > the existing test-suite target found in the top-level Makefile.am > as a starting point. While you can easily create, targets such > as xerces-p (to build) xerces-c-check (to test), and xerces-c-install > (install), other targets such as clean, distclean, and dist should > work throughout the distribution which might be more tricky. I > suggest that you check the Automake documentation to find out how > to this: > > http://sources.redhat.com/automake/automake.html > Right, thanks. My problem has been once there is a large existing set of autoconf/automake rules, it becomes really hard to understand how it all fits together. In the world of Perl, autoconf is not used - MakeMaker is, in the world of Java its Ant, in Ruby it's rake... So I'm really wanting to make sure I add the pieces into Xerces-C properly and not mess it up.. > For example, reading Section 13, "What Gets Cleaned", it appear that > you can use the clean-local and distclean-local to connect makefiles > in swig, something along these lines: > > clean-local: > $(MAKE) -C swig clean Ah! That helps. Because often I want the default targets generated for most sub-directories, for example swig/util/, but for other directories I need something special, say for swig/perl/. I'll look into this. Cheers, jas. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
