On May 22, 2006, at 4:50 PM, Arunkumar wrote:
Hi Curt,
I tried to build a release build (on a Windows XP SP2 machine) from
the
trunk and it failed.
I had set the classpath to point to: C:\Program Files\Microsoft Visual
Studio .NET 2003\Vc7\bin instead of the normal vc6 batch file. I
hope that
was not the reason for the failure.
Excerpt from the log file b4 the failure:
"
win-configure:
BUILD FAILED
C:\Documents and Settings\aviswanathan\My Documents\My
DevProjects\log4cxx\trunk\build.xml:385: Warning: Could not find file
C:\Documents and Settings\aviswanathan\My Documents\My
DevProjects\log4cxx\trunk\include\log4cxx\log4cxx.hw to copy.
"
Interesting. Does the specified .hw file exist in your checked out
copy? It does appear to be present in the SVN. Or did you use the
littletux tarball and perhaps it is missing that file.
I tried the debug build with the default classpath and it failed in
unit-tests.
Let me know if you need the exact log files.
Please. VC 6 is known to throw exceptions on some of the unit tests
that later versions of VC worked fine on. threadtest.cpp would fail
on all versions of VC, but it was removed from the test suite since
the idiom used in the test was broken, just broke earlier with VC.
A build related question:
In the INSTALL file it says you can pass optional parameters to the
build.
My question is can I pass them to the ant script or are they only
applicable
for "make" builds. For example: --enable-unicode and -with-thread
Microsoft
There is a bit of disconnect from the Ant options (see build options
around line 68 in INSTALL) and the autotool options (around line
227). The autotools options are stale (it mentions at line that at
line 113). For example, log4cxx now used APR and --with-
thread=Microsoft would be ignored. log4cxx (now) is always Unicode
enabled, but you do have the choice of specifying whether it uses
UTF-8 or wchar_t for the internal character type.
Probably would be helpful in Andreas could update the INSTALL file
for autotool.
