Community/Discussion/QNX4 Community Support (EOL)/XML/List of Posts
 
Forum Topic - XML:
   
Update
John Walsh
03/03/2009 9:13 AM
post23311
XML   
I am getting ready to make a simple XML file parser for QNX 4.25. But, I wanted to see if anyone has already got 
something or even started on something that I could take over. Has anyone out there attempted to use XML in 4.25 before?
Mario Charest
03/03/2009 9:14 AM
post23313
RE: XML   
Expat compiled pretty easy if I remember correctly.  I think TinyXml (C++) also worked nice.   All these are parser only
, can't use them to create XML data.


> -----Original Message-----
> From: John Walsh [mailto:community-noreply@qnx.com]
> Sent: March-03-09 9:13 AM
> To: qnx4-community
> Subject: XML
> 
> I am getting ready to make a simple XML file parser for QNX 4.25. But,
> I wanted to see if anyone has already got something or even started on
> something that I could take over. Has anyone out there attempted to use
> XML in 4.25 before?
> 
> _______________________________________________
> QNX4 Community Support
> http://community.qnx.com/sf/go/post23311
>
dave allamby(deleted)
03/04/2009 12:06 PM
post23494
Re: XML   
I ended up writing my own state driven push parser, so I can dump XML into it from file or TCP connection without having
 to sit in the middle of parser. Lets me process each field as it becomes available (not worried about XML well-formed 
issue) rather than wait till end of XML statement. As XML takes over as the defacto protocol of everything (including 
the machine control stuff we deal with), I decided that it was worth the effort to do my own rather than work around 
issues with open source/freeware stuff

For whats worth
Dave
Mario Charest
03/04/2009 12:11 PM
post23495
RE: XML   

> -----Original Message-----
> From: dave allamby [mailto:community-noreply@qnx.com]
> Sent: March-04-09 12:07 PM
> To: qnx4-community
> Subject: Re: XML
> 
> I ended up writing my own state driven push parser, so I can dump XML
> into it from file or TCP connection without having to sit in the middle
> of parser. Lets me process each field as it becomes available (not
> worried about XML well-formed issue) rather than wait till end of XML
> statement. As XML takes over as the defacto protocol of everything
> (including the machine control stuff we deal with), I decided that it
> was worth the effort to do my own rather than work around issues with
> open source/freeware stuff

I believe SAX parser will do just that, by design.

> 
> For whats worth
> Dave
> 
> 
> 
> _______________________________________________
> QNX4 Community Support
> http://community.qnx.com/sf/go/post23494
>
John Walsh
03/11/2009 2:35 PM
post24171
Re: RE: XML   
Thanks Mario and Dave. I tried Expat but had some issues with /sys/mman.h. The version I have apparently doesn't have 
madvise() and a few define statements. Also my version of <stdio.h> doesn’t have snprintf(), vsnprintf(), and a few 
others. I’ve been trying to find versions that will get it to compile but have yet to get it working. The print 
statements I think I could work around easy enough. But I’m at a loss as to another way to advise the kernel how to 
handle paging or if it is OK to just comment these calls out. 
   I’ll try the other suggestions. Thanks again.
Mario Charest
03/11/2009 7:01 PM
post24191
RE: RE: XML   

> -----Original Message-----
> From: John Walsh [mailto:community-noreply@qnx.com]
> Sent: March-11-09 2:36 PM
> To: qnx4-community
> Subject: Re: RE: XML
> 
> Thanks Mario and Dave. I tried Expat but had some issues with
> /sys/mman.h. The version I have apparently doesn't have madvise() and a
> few define statements. Also my version of <stdio.h> doesn’t have
> snprintf(), vsnprintf(), and a few others. I’ve been trying to find
> versions that will get it to compile but have yet to get it working.
> The print statements I think I could work around easy enough. But I’m
> at a loss as to another way to advise the kernel how to handle paging
> or if it is OK to just comment these calls out.
>    I’ll try the other suggestions. Thanks again.

Hum, don`t remember what version of expat I used but as far as I can remember it compile as is.  I do have snprintf and 
vsnprintf in our library though so it might have make it easier.

> 
> 
> _______________________________________________
> QNX4 Community Support
> http://community.qnx.com/sf/go/post24171
Thomas Fletcher
03/13/2009 12:01 PM
post24330
Re: XML   
John Walsh wrote:
>  Thanks Mario and Dave. I tried Expat but had some issues with
>  /sys/mman.h. The version I have apparently doesn't have madvise() and
>  a few define statements. Also my version of <stdio.h> doesn’t have
>  snprintf(), vsnprintf(), and a few others. I’ve been trying to find
>  versions that will get it to compile but have yet to get it working.
>  The print statements I think I could work around easy enough. But I’m
>  at a loss as to another way to advise the kernel how to handle paging
>  or if it is OK to just comment these calls out. I’ll try the other
>  suggestions. Thanks again.

You can probably chuck the madvise stuff code and the snprintf
and vsnprintf() just live in different headers ... but other than that
you should be able to get expat working ok.

Thomas
Mario Charest
03/13/2009 12:02 PM
post24332
RE: XML   

> -----Original Message-----
> From: Thomas Fletcher [mailto:community-noreply@qnx.com]
> Sent: March-13-09 12:02 PM
> To: qnx4-community
> Subject: Re: XML
> 
> John Walsh wrote:
> >  Thanks Mario and Dave. I tried Expat but had some issues with
> >  /sys/mman.h. The version I have apparently doesn't have madvise()
> and
> >  a few define statements. Also my version of <stdio.h> doesn’t have
> >  snprintf(), vsnprintf(), and a few others. I’ve been trying to find
> >  versions that will get it to compile but have yet to get it working.
> >  The print statements I think I could work around easy enough. But
> I’m
> >  at a loss as to another way to advise the kernel how to handle
> paging
> >  or if it is OK to just comment these calls out. I’ll try the other
> >  suggestions. Thanks again.
> 
> You can probably chuck the madvise stuff code and the snprintf
> and vsnprintf() just live in different headers ... but other than that
> you should be able to get expat working ok.
> 


I'm not sure but I believe that the expat I used provided its own version of *nprintf().

> Thomas
> 
> _______________________________________________
> QNX4 Community Support
> http://community.qnx.com/sf/go/post24330
John Walsh
03/16/2009 10:23 AM
post24426
Re: RE: XML   
Just downloaded the latest greatest version of Expat...2.0.1

I get all kinds of issues when I run ./configure most of which again look to be caused by headers. Did any of you figure
 out which version you got to configure and make OK under 4.25?  

I've attached the config.log. If anything jumps out at you...any advice would be greatly appreciated.
Attachment: Text config.log 55.75 KB

Return