Hi Dave, But the reason for doing this is eloquently expressed in this very thread--people were confused by this library's presence, and some thought they needed it around to use the parser.
The expression "you're damned if you do, you're damned if you don't" comes to mind here. :) Fortunately, judging by list traffic, while building the parser is something of a chore on Unices, folks don't have too much trouble on Windows. Cheers! Neil Neil Graham Manager, XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] 10/12/2004 05:36 PM Please respond to xerces-c-dev To [EMAIL PROTECTED] cc Subject Re: Missing xerces-c_2D.lib in xerces-c_2_6_0-windows_nt-msvc_60? > This was done intentionally. On no other platform > were both debug and release binaries both issued, > so it wasn't clear why this was being done on Windows. > No functionality is lost. Actually, functionality is lost, because you can no longer build debug executables for your applications that use Xerces-C, unless you are willing to re-build Xerces-C from source. The FAQ has several entries where it warns about mixing debug and release executables on Windows, and it's been a very common question on the mailing list over the past 6 years. Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
