You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by "dinesh kumar (JIRA)" <xe...@xml.apache.org> on 2010/09/04 12:52:37 UTC
[jira] Created: (XERCESC-1941) Xercesc-c++ does not build with ICU
4.0 when XERCES_USE_WIN32_MSGLOADER is replaced with
XERCES_USE_MSGLOADER_ICU proprocessor
Xercesc-c++ does not build with ICU 4.0 when XERCES_USE_WIN32_MSGLOADER is replaced with XERCES_USE_MSGLOADER_ICU proprocessor
--------------------------------------------------------------------------------------------------------------------------------
Key: XERCESC-1941
URL: https://issues.apache.org/jira/browse/XERCESC-1941
Project: Xerces-C++
Issue Type: Bug
Components: Build
Affects Versions: 3.1.1
Reporter: dinesh kumar
I was to test the ICU build if that works fine. I created a sample application which reads utf-8 encoding doc and while trying to write the cached document in to a seperate doc with different encoding (ICU supported encding e.g big5).
I am getting error that Xerces is unabke to create the converter for Big5. I build the xerces 3.1 with ICU, i used the default settings of the Xerces-all.vcproj with ICU build settings. Ideally Xerces should be able to create the converter.
Looking at the vcproj configurations , i found that XERCES_USE_WIN32_MSGLOADER is used as an pre-processor and in the code we have a special handling of XERCES_USE_MSGLOADER_ICU. On replacing XERCES_USE_WIN32_MSGLOADER with XERCES_USE_MSGLOADER_ICU, Xerces fails to compile completely and ask for providing the path for __imp__Xercesc_messages_3_1 dat.
How to verify that ICU build of xerces works fine.?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org