Thanks for the great info Earl. 

We will try these out with xerces 2.7 and xalan 1.10.

Ramkumar Devanathan
HP Software BTO R&D
Bangalore
India
PHONE: (91)-80-2205-2219

-----Original Message-----
From: Earl Woodman [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, July 03, 2007 9:33 PM
To: xalan-dev@xml.apache.org
Subject: Re: FW: VS2005 support for Xerces and Xalan - Windows x64

Hi,

I have had success building Xerces and Xalan on VS2005 (x86)  with the
/Zc:wchar_t flag turned on, although the versions I am using are Xerces
2.4 and Xalan 1.7. Here's a quick overview of what I did:

For Xerces, I created a VC8 project by upgrading the VC6 project. It
will not work if you upgrade from VC7 project files!

For Xalan, I had to change the usage of one call to CreateFileW to go
back to CreateFileA. There are also some other gotchas, like the
Localization project won't read in parameters from tools.ini when using
nmake inside the VS2005 environment. Also you will need to build Xalan
with these preprocessor defines: XALAN_XALANDOMCHAR_USHORT_MISMATCH and 
XALAN_USE_WCHAR_CAST_HACK.

Good luck,
Earl




On Tue, Jul 03, 2007 at 08:47:53AM -0700, David Bertoni wrote:
> Devanathan, Ramkumar (HP Software BTO) wrote:
> > Hi all, I need to know by when the official support of Xerces and
Xalan
> > on VS2005 (x86 and x86_64) build is going to be available. Is there
a
> > way this can be expedited?
> 
> Xalan-C cannot release until Xerces-C has released, so there's nothing
we 
> can do.  If you want to help expedite the release, you can volunteer
to 
> help with sorting out the Xerces-C build issues.  There have been
several 
> discussions on the Xerces-C Developer list on this very subject.
> 
> Dave
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

-- 
Earl Woodman
Senior Software Engineer - IONA | Making Software Work Together TM.
Email: [EMAIL PROTECTED]
Phone: 709-738-3725 x.29
WWW: http://www.iona.com/

---------------------------------------------------------------------
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]

Reply via email to