Hi Jason, Jason Stewart <[EMAIL PROTECTED]> writes:
> On 13/03/2008, Boris Kolpackov <[EMAIL PROTECTED]> wrote: > > > BTW, if you make swig build by default (and that's what what > > happens if you add it to SUBDIRS in top-level Makefile.am), you > > need to make sure that all other build targets are also implemented. > > These include 'all', 'clean', 'distclean', 'install', and 'dist'. > > Normally, automake takes care of this but since you use a different > > build system (Makefile.PL), you will need to make sure that these > > targets are implemented properly. > > Since I am not wanting to make the components in swig/ by default, is > this still important? There would be problems with the 'all' target - > right now it means 'make perl', but later with more target languages > it wouldn't make sense, so why implement it now? 'dist' and 'install' > are the same, but 'clean', and 'distclean' are useful and I will > implement them regardless. Sorry, I missed this email. I think we first need to decide how to split swig. If we leave something "buildable" in Xerces-C++ (that will be included in the build if configured with --with-swig) then we need to support all those targets. Hopefully the only thin we will need to build is util which will use automake so this will all be taken care automatically. Boris -- Boris Kolpackov, Code Synthesis Tools Open source XML data binding for C++: http://codesynthesis.com/products/xsd Mobile/embedded validating XML parsing: http://codesynthesis.com/products/xsde --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
