Hi Nick,

I too hit some major snags when porting Xerces to VxWorks 6.8. 

The major issues I'm seeing is the incomplete and spotty implementation
of Wind River's POSIX "Compliant" interfaces (quotes are intentional).
I'm guessing that anyone who's tried the port has run into this and
moved on to something else less troublesome. Not the fault of the Xerces
development team, to be fair.

It looks like with some effort that the holes can all be worked around,
but I don't have sufficient time to hunt it all down and provide
replacement functions for the stuff that's missing just now.

I'll take a look at the Expat port from Wind River. However, based on my
experience with WRS, I'd be willing to bet there's trimmed out
functionality that I'd like to have for what I'm doing.

Thanks for your information,
Bill


-----Original Message-----
From: nelkherj [mailto:[email protected]] 
Sent: Tuesday, August 24, 2010 4:59 AM
To: [email protected]
Subject: Re: Xerces port for VxWorks 6.x using POSIX

Bill,

I recently re-sent an email asking for help about xerces support for
vxWorks 
6.x.  Beside Boris's response to me a few months ago about a similar
situation 
using another OS, no one seems to have built xerces with vxWorks 6.x.

I also found out from Windriver that they don't know of any user who is
using 
xerces with vxWorks 6.x.  I was able to build the xerces code but hit a
snag 
when I tried to build the ICU library.  That is why I decided to move to
Expat 
which is offered as part of the webservices component from Windriver.

If you or someone else on this board knows of someone who was able to
build it, 
please have them share this information with us.

Thanks,
Nick




----- Original Message ----
From: "Howell, Bill" <[email protected]>
To: [email protected]
Sent: Thu, August 19, 2010 2:04:04 PM
Subject: Xerces port for VxWorks 6.x using POSIX

Could somebody direct me to any information about getting the Xerces
libraries built and running on a VxWorks 6.x platform?

I need to migrate the build into the managed build interface of the
WindRiver Workbench (which is essentially Eclipse with some custom
plugins), rather than rely on the provided automake, so information
about gcc 4.1 compiler flags and preprocessor defines would be very
welcome.

Also, if someone has done this and could provide information about their
experience, I would appreciate it very much.

Bill Howell
Senior Software Engineer
FLIR Systems, Inc.



Notice to recipient: This email is meant for only the intended recipient
of the 
transmission, and may be a communication privileged by law, subject to
export 
control restrictions or that otherwise contains proprietary information.
If you 
receive this email by mistake, please notify us immediately by replying
to this 
message and then destroy it and do not review, disclose, copy or
distribute it.  
Thank you in advance for your cooperation.



      

Notice to recipient: This email is meant for only the intended recipient of the 
transmission, and may be a communication privileged by law, subject to export 
control restrictions or that otherwise contains proprietary information.  If 
you receive this email by mistake, please notify us immediately by replying to 
this message and then destroy it and do not review, disclose, copy or 
distribute it.  Thank you in advance for your cooperation.

Reply via email to