Will try autotools, but what about the error that I get while building
on windows vc++ 6. fails while running the unit tests.
[delete] Deleting:
C:\logging-log4cxx\build\debug\shared\log4cxx.properties
[delete] Deleting: C:\logging-log4cxx\build\debug\shared\log4j.properties
[exec] .
[exec] OK (1 tests)
[exec] .
[exec] OK (1 tests)
[exec] .
[exec] OK (1 tests)
clean-output:
[delete] Deleting 97 files from C:\logging-log4cxx\tests
run-unittest:
[exec] ............................Assertion failed: stat ==
APR_SUCCESS, f
ile C:\logging-log4cxx\tests\src\util\transformer.cpp, line 212
[exec] abnormal program termination
BUILD FAILED
C:\logging-log4cxx\build.xml:1141: exec returned: 3
Total time: 9 seconds
C:\logging-log4cxx>
thanks
aditya
Curt Arnold wrote:
On May 23, 2007, at 9:59 AM, Marshall Powers wrote:
I'm not sure, but I would guess that ant is not making the compiler
link the
expat library. I had similar problems building my program with
log4cxx on
solaris. Try to run the configure script for APR-Util to see if it
tries to
link the expat library, and then see if the ant build file does the
same.
Good Luck,
Marshall
P.S.
I wonder why the Log4cxx developers insist on using the <cc> task to
build
APR and APR-Util when those libraries come with their own autotools
scripts,
Makefiles, etc...
We try to support both autotools/makefiles and Ant. The cc task us
helpful since it supports Microsoft Visual C++ and other non-Unixy
compilers and can generate project files for several IDEs. I thought
the Ant build worked with Solaris 10, though I haven't tested Solaris
9. Sounds like you would be better off just sticking with the
autotools build.
