DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4958>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4958 Xalan Doesn't Run with MSVC 7.0 (aka Visual C++ .NET) [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From [EMAIL PROTECTED] 2001-11-21 13:20 ------- MSVCP60.dll is something that Microsoft distributes with their operating systems. Although we could legally re-distribute it, we don't do that. The other issue is that you shouldn't attempt to link applications built with MSVC 7.0 against libraries built with earlier versions, as you'll end up with multiple run-time libraries. You should rebuild Xalan under 7.0 if you want to use it in this manner. The only problem with defined XALAN_XALANDOMCHAR_USHORT_MISMATCH is that it will result in inefficient transcoding. We need to coordinate a fix for this with Xerces, so that we use wchar_t on platforms where it is a distinct type, it's a 16-bit value, and we know that it contains Unicode code points. AIX is one such platform, and Windows will be with MSVC 7.0. Your best bet for the time being is to disable wchar_t as a distinct type. There's an option to do this so that it's compatible with 6.0.
