Re: Xerces C++ Lib on Window NT using CodeWarrior

["Michael D. Crawford" <cr...@goingware.com>]

> Does any one have any experience building Xerces C++ library on Windows NT
> with CodeWarrior compiler  ?

I did it last year.  I have a project and the platform specific files that work
OK with it.

The main problem is that the Win32Transcoder provided by Xerces, at least at the
time I did it, used Microsoft-specific extensions to the C standard library that
are not supported by CodeWarrior.

I built it as a static-link library, as it was meant for a downloadable consumer
product that I wouldn't want to risk the users being confused by DLL
management.  It should be straightforward to take what I have and make a DLL out
of it.

It's for what's now an old version of Xerces, so a little work will be required
to update the project for any changes in what source files are included.

I also had it working with CodeWarrior on the Mac OS at the time too.  I had a
problem that when I would transfer files from my PC to my Mac a couple of long
filenames would get truncated, which CodeWarrior for the Mac could deal with,
but transferring the files back would end up with files with all or part of
their extension missing, which CodeWarrior for Windows could not deal with - so
I'd have to fix the filenames after every file transfer.  

But then I tried out a couple filesharing solutions (Thursby DAVE or samba and
netatalk running on a third machine running Linux) and while it meant I didn't
have to transfer archives back and forth all the time, the files would either be
hidden or presented in their 8.3 form.  Uck.

I have this on an old backup.  I can't deal with it tonight but tomorrow night I
should be able to get it for you and stick it on my website somewhere, I'll post
a URL when I do.

I didn't finish the job, but I also did a great deal of work towards porting ICU
to build under CodeWarrior.  I did this on Windows, in preparation for moving it
to the Mac, but I sort of had a meltdown when I discovered the use of memory
mapped files.  This turned out not to be insurmountable but I found it easier to
just write a really lame transcoder for my own project.

I think it would be just dandy if someone would take the Windows CodeWarrior
projects and include them with the regular xerces source distribution.  You
could put XML export files in CVS.  This after they're updated of course.

Oh, one more thing - there was an assumption in the configuration header file
that if the compiler was codewarrior then the platform was macintosh. 
Considering that CodeWarrior is available for a great many platforms (not just
mac and windows, but PalmOS, game consoles and a lot of embedded systems) it's
important to distinguish the platform.

Mike
-- 
Michael D. Crawford
GoingWare Inc. - Expert Software Development and Consulting
http://www.goingware.com
crawford@goingware.com

  Tilting at Windmills for a Better Tomorrow.

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org