Hi Boris, I am able to get xerces 3.1.0 to build until it stops with this error message "configure: error: Xerces cannot function without a transcoder", which is expected.
My problem now is in building the icu library. I followed the instructions on the ICU website but so far I have not been successful. I am having a problem when I am building the host build, buildB. It does not build any of the libraries, like "icutu". I am looking into it, but if you or others have been able to build the icu successfully, I appreciate your input. Thanks, Nick ----- Original Message ---- From: Boris Kolpackov <[email protected]> To: [email protected] Sent: Fri, April 30, 2010 7:23:12 AM Subject: Re: xerces - vxWorks 6.x for PowerPC Hi Nick, nelkherj <[email protected]> writes: > Hi, > > Has anyone been successful in building a recent version of the xerces > library for vxWorks v6.x running on a PowerPC? I haven't tried it on VxWorks but I have done so for LynxOS and I think it should be possible for VxWorks 6.x. The only potentially problematic area is the transcoder implementation. I would first try --enable-transcoder-iconv and if that doesn't work (as on LynxOS) then you will need to build ICU for VxWorks and configure Xerces-C++ to use that. Cross-compiling ICU is a tricky task which is described in this earlier post: http://marc.info/?l=xerces-c-users&m=123926824206247&w=2 > PS: I have tried to build it and searched vxWorks and xerces FAQs with > no luck. What exactly didn't work when you tried to build it? Boris -- Boris Kolpackov, Code Synthesis http://codesynthesis.com/~boris/blog Open-source XML data binding for C++ http://codesynthesis.com/products/xsd XML data binding for embedded systems http://codesynthesis.com/products/xsde Command line interface to C++ compiler http://codesynthesis.com/projects/cli
