Hi Curt,

I am using Visual Studio 6.0

In version log4cxx-0.9.7, Unicode Release build is also provided. So as in
my project I am using the macro UNICODE for Unicode build, I am not getting
any errors. But when I use the DLL of log4cxx 0.10.0 directly, I get the
errors during the string conversions. 

Also I could not build the ANT build as I could not exactly get the versions
of the Jars which were specified in INSTALL file. When I used their latest
versions I was getting some build errors. Is it possible to make the build
using Visual Studio?

One more question - 
I read the line "The log4cxx distributions contain only sources.
log4cxx-0.9.7 is significantly out of date" . So should we continue to use
log4cxx version 0.9.7 in our project.


-Rajan

-----Original Message-----
From: Curt Arnold [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, July 24, 2007 9:30 PM
To: Log4CXX User
Subject: Re: Appender question


On Jul 24, 2007, at 7:35 AM, Rajan Phatak wrote:

> Hi All,
>
>
>
> What is the latest version for log4cx= x is available supporting  
> Unicode characters?
>
> I have got the version "log4cxx= 0.10.0" for which I am not able to  
> build Unicode Release Build. Can somebody help me= in getting the  
> code which can be built using Microsoft Visual Studio supporting  
> Unicode?

The current SVN HEAD supports both single-byte and Unicode characters  
in one build.  There is not a distinct Unicode and non-Unicode build.

What version of Visual Studio are you using?
What exact problems are being reported?
Are you able to successfully build log4cxx using the Ant build?
How or where did you get your VS project?

I expect to have a first release candidate for log4cxx 0.10.0 this  
week and it will come prepackaged with a VS project generated from  
the Ant build.



DISCLAIMER
==========
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Pvt. Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Pvt. Ltd. does not accept any liability for virus infected mails.

Reply via email to