I ran into the same wstring issue on cygwin. Your hint helps, but as soon as its gets to log4cxx/helper/loglog.h and sees the wstring& (line 92), it fails. So, its the same as HPUX 11.
Doing solaris next, and then (shudder) aix.
cheers, [EMAIL PROTECTED]
Curt Arnold wrote:
The code was designed to support logchar as being wchar_t or UTF-8 char's. However, the support routines for UTF-8 chars was not coded since at the time I didn't have apr-iconv integrated.
Right now, use of wchar_t is hardcoded by the
#define LOG4CXX_LOGCHAR_IS_WCHAR 1
in logstring.h
If you change this to:
#define LOG4CXX_LOGCHAR_IS_CHAR 1
log4cxx should compile but fail to link due to unsatisfied references.
Obviously this should be parameterized in the build. I'll make a stab at supplying the missing functions.
I thought it likely that this could affect cygwin and/or MinGW too. Did you make any progess with hacking the build file?
On Mar 10, 2005, at 3:22 PM, Jwahar Bammi wrote:
Curt/List,
We have a small problem on platforms that dont support wstring and the current CVS Head, for example HPUX 11.0
(there is a mode of aCC -AA that supports wstring, but that is incompatible with how most code on the platform is compiled).
(see reasons for non-support of wstring in libstdc++ here:
http://gcc.gnu.org/ml/libstdc++/2003-07/msg00368.html
)
I am not sure how do we approach this: dont support such platforms? Conditionalize the code for such platforms? Does APR assist any on these platforms?
0.9.7 did not use wstring so this never came up. I am kicking myself for not trying cvs a little sooner.
cheers,
-- Jwahar Bammi [EMAIL PROTECTED]
-- Jwahar Bammi [EMAIL PROTECTED]
