public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
* [ECOS] xml parser
@ 2004-06-13  7:53 Diego Duyvejonck
  2004-06-13 12:46 ` Gary Thomas
  0 siblings, 1 reply; 3+ messages in thread
From: Diego Duyvejonck @ 2004-06-13  7:53 UTC (permalink / raw)
  To: ecos-discuss

Hi,

I would like to implement an XML parser that runs with eCos (powerpc
platform).  Libxml2 would be an interesting choice.  Has anyone tried to
build this library ?
Running configuration (from the unpacked libxml2 SRPM directory -
xmlsoft.org) confirms that a cross compiler 'powerpc-unknown-eabi' (?) is
used...
I get the libxml.a library file by running the generated MakeFile.  But
still, I cannot get that library file to work with my eCos project.  It
doesn't compile (reports missing header file e.g. "iconv.h", ...).  My own
MakeFile seems ok  -> the location of the libxml2 header files and library
is set correctly.

best regards,
Diego Duyvejonck


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [ECOS] xml parser
  2004-06-13  7:53 [ECOS] xml parser Diego Duyvejonck
@ 2004-06-13 12:46 ` Gary Thomas
  0 siblings, 0 replies; 3+ messages in thread
From: Gary Thomas @ 2004-06-13 12:46 UTC (permalink / raw)
  To: Diego Duyvejonck; +Cc: ecos-discuss

On Sun, 2004-06-13 at 01:53, Diego Duyvejonck wrote:
> Hi,
> 
> I would like to implement an XML parser that runs with eCos (powerpc
> platform).  Libxml2 would be an interesting choice.  Has anyone tried to
> build this library ?
> Running configuration (from the unpacked libxml2 SRPM directory -
> xmlsoft.org) confirms that a cross compiler 'powerpc-unknown-eabi' (?) is
> used...
> I get the libxml.a library file by running the generated MakeFile.  But
> still, I cannot get that library file to work with my eCos project.  It
> doesn't compile (reports missing header file e.g. "iconv.h", ...).  My own
> MakeFile seems ok  -> the location of the libxml2 header files and library
> is set correctly.

Compiling external code and getting it hooked together with the eCos 
and applications can sometimes be a challenge, especially if that 
external package has it's own Makefile(s), etc.

You might try looking at some of my examples:
  http://www.mlbassoc.com/examples/
In particular, the NetPiPe example shows how external packages can be
combined with the eCos kernel to build up a complete eCos application.

You also might send more detail, e.g. the actual Makefile(s) and command
lines that you used, to the list and then we would be better able to
comment.

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [ECOS] xml parser
@ 2004-06-14  6:11 eibach
  0 siblings, 0 replies; 3+ messages in thread
From: eibach @ 2004-06-14  6:11 UTC (permalink / raw)
  To: diego.duyvejonck; +Cc: ecos-discuss

Hello,

maybe http://www.grinninglizard.com/tinyxml/ is worth a look (if you want to have a DOM parser). It is not a library but compiled and linked together with your application sources. It works fine for me.
http://expat.sourceforge.net/ is a good choice if you prefer a SAX parser. It is a library an can easily be adapted to ecos.

Regards,
Dirk

To: diego.duyvejonck@skynet.be
Cc: ecos-discuss@sources.redhat.com


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2004-06-14  6:11 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-06-13  7:53 [ECOS] xml parser Diego Duyvejonck
2004-06-13 12:46 ` Gary Thomas
2004-06-14  6:11 eibach

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).