If you have reasonable unix experience plus a C compiler, then it should be quite straight forward to:
1. Download the gcc g++ source, build the C++ compiler then compile the XERCES libraries on your platform. 2. The biggest problems we have faced are with the opensource autoconf, gzip, and all the other bits you need to perform a full and complete re-build. 3. So if for instance you have a copy of g++ and associated tools downloadable in binary form for your platform you are almost certainly there. 4. Depending on the general C/UNIX experience you might get it done in a couple of days. With a bright new graduate to do the donkey work a couple of weeks is more realistic. 5. The key issue will be whether your platform is similar in architecture to another platform in terms of OS compatibility and architecture such as little endian / big endian. 5. We ported to tru-64 some time ago using a very experienced person (though that is now in the list of options), and then re-built on HP 10.2 using g++ and on Sequent using g++ following option 4. That was though just a build of existing options. There is reasonable documentation within the XERCES release to talk you through adding another OS into the build utilities. 6. I guess the real issue is how much testing you need to do?! Nick -----Original Message----- From: Jones Gwyn [mailto:[EMAIL PROTECTED]] Sent: 18 October 2001 17:28 To: '[EMAIL PROTECTED]' Subject: Xerces-C porting effort? Can anyone with some experience of porting Xerces-C give me advice? I am trying to work out the effort required to do a port to the Siemens BS2000/OSD mainframe environment. This is based on standard microprocessors (Risc) and /390 architecture. It has POSIX support, but the couple of developers involved do not have a whole lot of 'make' or open-source porting experience. Just roughly, are we talking say: A couple of weeks understanding the whole thing A couple of weeks actually implementing changes A couple of weeks trying to resolve problems A couple of weeks contingency Or is that way off the mark? Which of the current ports might be the best starting point? Roughly how problematic are these ports from scratch? Thanks, Gwyn. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ************************************************************************* This message contains privileged and confidential information intended only for the use of the recipient named above. Its contents do not constitute a commitment by Strategic Thought Limited ("Strategic Thought") unless separately endorsed by an authorised representative of Strategic Thought. Any use, dissemination, distribution, reproduction or unauthorised disclosure of this message is prohibited. If you receive this message in error, please notify the sender immediately and delete it from your computer systems. Any views expressed in this message are those of the individual sender and may not necessarily reflect those of Strategic Thought. Strategic Thought believes this e-mail and any attachments to be virus free. However, the recipient is responsible for ensuring it is virus free and Strategic Thought do not accept any responsibility for any loss or damage howsoever caused from use of this e-mail, attachments or contents. ************************************************************************* --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
