The primary work of a port involved creating:
1) A new compiler header for the compiler
2) A new platform utilities file that implements the little bit of system
access we need, and an associated header.
3) Updating XML4CDefs.hpp and AutoSense.hpp to get your new headers
included when compiled under your OS and compiler.
Other concerns are:
1) Does ICU compile on your platform? If not, then you'll need to do a
transcoder implementation that uses your local transcoding services. I
assume that the Iconv transcoder would work for you, though perhaps with
some modifications.
2) What message loader will you use. For starting off, you can use the 'in
memory' one which is very simple and easy. Then, once you get going, you'll
want to possibly adapt the message catalog message loader or write one of
your own that uses local services of some sort.
----------------------------------------
Dean Roddey
Software Weenie
IBM Center for Java Technology - Silicon Valley
[EMAIL PROTECTED]
Gary Gale x58814 GB- COM/Q/6th <[EMAIL PROTECTED]> on 01/28/2000
06:06:47 AM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Port of Xerces to Digital Unix/Compaq Tru64?
A while back, a port of XML4C++ for the above platform was mentioned on
IBM's
alphaworks discussion board, although it never did seem to appear.
Is there a port in progress of Xerces for DEC Unix/Tru64 4.0f that anyone
knows
of. If not then I'm going to have to roll my sleeves up and attempt it
myself.
If this is the case, it looks as if I will have to not only add header
files
and macro definitions, as described in the FAQ, but also to modify the
autoconf/automake scripts as the platform name, required in the Makefiles
still
keeps appearing as "UNKNOWN" despite the header file changes.
Any pointers and advice gratefully received (and any pitfalls that anyone
has
already encountered).
Best regards,
Gary
--
Gary Gale Mail: [EMAIL PROTECTED]
UK Server Group Phone: +44 (0) 171 542 8814
Factiva, A Dow Jones & Reuters Company Web: www.factiva.com
