Building when RTL doesn't support wchar_t (was Re: INSTALL and web site update)

[Curt Arnold <ca...@apache.org>]

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
> bammi@memento-inc.com
>
>

Re: Building when RTL doesn't support wchar_t (was Re: INSTALL and web site update)

[Jwahar Bammi <ba...@memento-inc.com>]

i hacked the build file and made some progress. I hacked the build file 
a little more to help it recognize my use of -Dapr.dir=/usr/local/apr 
(the naming conventions its using dont fit cygwin, so the conditional 
apr-available etc were not getting set).

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,
bammi@memento-inc.com

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
>> bammi@memento-inc.com
>>
>>
>
>
>

-- 
Jwahar Bammi
bammi@memento-inc.com