[Expat-discuss] darwin and expat
Joe Stacy
joe at switchgearsoftware.com
Thu May 18 19:40:19 CEST 2006
I do want the rest of my app to be Unicode - apologies if I implied
otherwise.
Specifically, building in Darwin with these macros defined, I get an
error with xmlwf/unixfilemap.c due to conflicting definitions of
filemap(). Filemap.h selects the wchar_t signature while unixfilemap.c
uses char.
If xmlwf is not required, is there a proper way to remove it from the
build or should I just yank it from the makefile?
-----Original Message-----
From: Karl Waclawek [mailto:karl at waclawek.net]
Sent: Thursday, May 18, 2006 7:19 AM
To: Joe Stacy
Cc: expat-discuss at libexpat.org
Subject: Re: [Expat-discuss] darwin and expat
Joe Stacy wrote:
> I'm trying to build expat on Darwin in a cross platform project. Since
> I'm further wrapping expat with a DOM, I'm trying to keep my wrapping
> code platform independent and it's all Unicode. I have XML_UNICODE and
> XML_UNICODE_WCHAR_T macros defined and it appears that the file
> xmlwf/unixfilemap.c does not implement a wchar_t flavor of the
filemap()
> function. Is there something I'm missing or have configured
incorrectly
> or is it a simple matter of functionality that needs implemented?
>
These are two different issues. XML_UNICODE and XML_UNICODE_WCHAR_T
merely
define which encoding Expat uses to report back to the application. It
does not force
all of your application to be wchar_t based, although that would be a
good idea.
Btw, regardless of how you build Expat, it always uses Unicode. Its just
the encoding
that can vary, that is: UTF-8 or UTF-16.
So, what problem are you running into? xmlwf is not necessary for an
application to use Expat.
Its just a helper program, you don't need to build it.
Karl
More information about the Expat-discuss
mailing list