Hello, I have to challenge the inclusion of Log4cxx in out projects based on an old Borland Build 5 and 6. We already tried log4cpp but need the SMTPAppender and rolling FileAppender which are not provided by log4cpp as we need them.
I first tried the ant build of log4cpp but it doesn't seem to be fully compatible with the old Borland anymore. I got it compiling after little changes to build.xml but in the end I'm stuck with a linker error where Borland just provides an error code. Afterwards I tried building with my own, newly created project and did manage to get it to compile and create a static library. I used some binary distributions of apr to link against because i didn't manage to get apr built on my own, yet. When I try to use my own created log4cxx.lib in a test program, I get a linker error which I don't understand the meaning of. The error is the following: [Linker Fehler] Unresolved external 'std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string<char, std::char_traits<char>, std::allocator<char> >(int, int, const std::allocator<char>&)' referenced from D:\BENUTZER\TSCHOENING\EIGENE DATEIEN\BIBLIOTHEKEN\TRUNK\C++\LOG4CXX\SRC\MAIN\CPP\PROJECT1.LIB|cacheddateformat The same error sometimes is shown with syslogappender as source class. Any hints on what might be the error? I think it's maybe related to LogChar, because the error does change whether or not LOG4CXX_LOGCHAR_IS_UTF8 or LOG4CXX_LOGCHAR_IS_WCHAR is set. Depending on the define the error stats basic_string<char.. oder basic_string<wchar_t... But I always have the linker error. I do use std::string etc. in Borland Builder, so I think it should work in general. Thanks for any help. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning AM-SoFT IT-Systeme - Hameln | Potsdam | Leipzig Telefon: Potsdam: 0331-743881-0 E-Mail: tschoen...@am-soft.de Web: http://www.am-soft.de AM-SoFT GmbH IT-Systeme, Konsumhof 1-5, 14482 Potsdam Amtsgericht Potsdam HRB 21278 P, Geschäftsführer: Andreas Muchow
