On Feb 9, 2008, at 8:12 AM, Jonathan Wakely wrote:
I've just checked log4cxx out from subversion but am unable to even
build it:
$ ./autogen.sh
configure.in:40: installing `./missing'
configure.in:40: installing `./install-sh'
src/examples/cpp/Makefile.am: installing `./depcomp'
configure.in:441: required file `src/performance/Makefile.in' not
found
configure.in:441: required file `src/performance/cpp/Makefile.in'
not found
configure.in:441: required file `src/performance/cpp/xml/
Makefile.in' not found
I tried running configure anyway, but it died with:
configure: creating ./config.status
config.status: error: cannot find input file: Makefile.in
No Makefile, so I can't use the autotools approach.
Been doing a release candidate preparation and just recently removed
the src/performance directory (https://issues.apache.org/jira/browse/LOGCXX-232
) since a lot of it was code data files that were carried over from
log4j and they were dead even in log4j. I removed "performance" from
src/Makefile.am, but missed a few references. That has been fixed in
rev 620192. Should work now.
I tried to follow the instructions in INSTALL for building with ant,
but ant-contrib doesn't install cpptasks.jar on my system so that
fails too (i have the ant-contrib-1.0-0.4.b2.fc6 RPM installed on
Fedora 8.) I tried downloading ant-contrib-1.0b3 from SourceForge but
that doesn't contain cpptasks.jar either.
Ant-contrib provides two different products, ant-contribs proper and
cpptasks. They have always been distributed separately. But anyway,
as part of the release candidate preparation, I've been modifying the
ant script to generate Xcode and Visual Studio project files that have
the appropriate Apache license notices and project dependencies.
That has requires making modifications to cpptasks, so the Ant build
file requires building cpptasks from its SVN at the moment. The plan
is to get a release candidate out for review for log4cxx using the SVN
HEAD of cpptasks, then work on a release of cpptasks and then come out
with a release candidate of log4cxx for a vote. The changes that have
required updated cpptasks have had the specific cpptasks SVN revision
required as
The Short Introduction to log4cxx says it's a popular logging
framework for C++, but half the wiki pages I looked at for build
instructions were blank and it seems to be far from complete.
The build process has been changing as we have been pushing for a
release candidate and as typical the documentation is lagging. As
things are almost finished with the build modifications, writing up
the new documentation is up next. The release will have formal build
documentation as part of the release and on the log4cxx web site.
Will need to remove obsolete instructions from the Wiki.
Should
I expect to be able to build the lib from subversion? If not, how do
I go about reviewing the lib and deciding whether to contribute to it,
rather than creating yet another C++ logging framework?
(log4cpp and log4cplus both have non-trivial problems with their
implementations, I was hoping to see if this library was any better,
but you don't make it easy!)
A release has been long long overdue and there have been substantial
modifications necessary in very short timeframe unfortunately there
have been inadvertent breakages of the SVN build and the documentation
has lagged. The goal is to make the build much easier and better
documented, however the path from where we were to where we are has
not been a little rocky.
Am I just being stupid or is it as difficult as it seems to build
the library?
Jonathan
You just jumped in at the time that a whole lot of things were
changing in the SVN.
