Hi Jason, Jason Stewart <[EMAIL PROTECTED]> writes:
> interfaces/ and util/ are independent and perl/ is Perl-dependent. What about the Perl subdirectory in interfaces/ as well as the scripts/ directory? We would want to leave only the minimum, language-independent code in swig. > > 1. If we move just the Perl part, then we can probably leave the > > swig proper in Xerces-C++ which can be used by Xerces-P as well > > as other language binding if they are created in the future. > > I favor this idea. Yes, I also prefer this split-up. As you suggest we can have the --with-swig option which triggers building the library in util/. It also seems to me that you want to put Xerces-C++ inside Xerces-P instead of simply make Xerces-P depend on Xerces-C++. Perhaps you have your reasons, but if we decide to go the dependency way then we need to think about what needs to be installed and where from the swig directory (for reasons why we need to install things, see an email from Jay in this thread). 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]
