I know from some previous posts that a release requires a vote process and it
could take long. But getting sources from svn head and build doesn't look
attractive at all. Trying to check out code and build could get into a
situation I have today: the code is not compilable. I have seen watch
log4cxx since 2004. I tried to use log4cxx at that time and found 0.9.7 is
said to be very buggy and 0.9.8 is on the way, so I dropped log4cxx and used
some proprietary logging software. Recently I want to try log4cxx again and
found 0.9.8 is not released and 0.10.0 is on the way. This is not meant to
complain, I understand that log4cxx is an open source project, people are
contributing their own time for free. But if there is no usable release,
potential users will go away and contributers' time to this project would be
largely wasted, cause the project is not used by anyone in the past 2 years.
I know another group in my firm choose log4cpp instead. log4cpp is not as
feature rich as log4cxx, but it can be built easily. people with basic
logging need(I think a lot of users fall in this category) can use it with
ease.
sorry if this offends anyone, that is not my intention. I come from log4j, I
really like to see log4cxx's user base grow and become the first choice when
people come to c++ logging.
A few ideas for building log4cxx in a self-contained manner:
1. it would be nice to have build dependencies like cpptasks.jar and
ant-contrib.jar shipped with the build or automatically downloaded from the
web
2. provide option to link apr statically, I notice ant build has such an
option. subversion, as of 1.4, requires apr 0.9x.
--
View this message in context:
http://www.nabble.com/when-where-can-we-get-a-usable-log4cxx-release-tf2495572.html#a6957283
Sent from the Log4cxx - Users mailing list archive at Nabble.com.
|
