Hi, I have a couple of questions/concerns about the new autotools-based build system in the trunk (upcoming 3.0):
1. Why rename libxerces-c.so/.a to libxerces.so/.a? This makes the job of supporting both 3.0 and older releases more complicated (the interface differences are relatively easy to resolve with the preprocessor). 2. Why factor out messages to a separate library (libXercesMessages) that the application developer has to link to? This makes it more difficult to support both 3.0 and older releases. Also, AFAICS, this is not done for Windows builds. Can this at least be made optional via a configure option? BTW, this library is not installed (see below). 3. Why build all those libraries (libdom, libinternal, etc.)? They are not installed so it seems their only purpose is to take up space and slow down the build speed. The last one is more of a bug report than a question: when I try to install Xerces-C++, I get No rule to make target `res-install', needed by `install' in the src/xercesc/util/MsgLoaders/ICU/Makefile.in. It seems the res-install target is left unimplemented there as well as in src/xercesc/util/MsgLoaders/MsgCatalog/Makefile.in. Any idea on what's going here? Thanks, Boris -- Boris Kolpackov Code Synthesis Tools CC http://www.codesynthesis.com Open-Source, Cross-Platform C++ XML Data Binding --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
