Tommi M�kitalo wrote:
Hi,
I'm not a ant-user. I use autoconf/automake for my own programs. So I try to compile log4cxx with autoconf/automake.
I'm not an autoconf/automake guy. Definitely the plan is to get the other build systems up to speed, but I start with an Ant build since it readily supports both the Win32 and GCC toolchain and work outwards. If you'd like to take the lead on getting autoconf/automake updated for APR, it would be helpful since I'm still iterating on other issues.
This triggers an error, if apr-headers are not found. On my system (still SuSE 9.2 x86-64) I need to help configure by runnig configure withI have heard that there is a autoconf macro/script/something that will find the right include path for APR. If it isn't obvious, ask on the apr-dev mailing list and they should know what I'm talking about.
./configure CPPFLAGS=-I/usr/include/apache2
The buildsystem finds apr-headers then.
/usr/include/apache2 will find the 0.9.x series of APR currently in use in Apache. I don't think that we depend on anything that is APR 1.x specific, but if we have to make a choice will favor 1.0 since it is the current release..
I wonder why you declare apr_int64_t in log4cxx-headers. apr_int64_t is defined in apr_atomic.h, so if you need it, include this header.I've avoided including APR headers in the log4cxx headers to eliminate the need for applications that are using log4cxx to have to add APR to their include path. I'm able to use forward declarations for apr_pool_t, apr_iconv_t and others. I'll review the definition for apr_int64_t, but I'll resort to some other mechanism to forward declare it before including APR headers in log4cxx headers.
