On Aug 7, 2006, at 8:10 AM, bilinmek istemiyor wrote:

Hello,

I am very much new to C++ programming in MS Windows environment. I am asked to develop a C++ application with QT 3.2.3 on Windows platform with MS Visual C++ 7.1 .Net edition. I have been developing C programs mostly on solaris and linux platforms.

After realizing that Qt 3.2.3 does not have a logging API other then some qDebug, qFatal, qWarning, I have seached for a logging library and found three different log4c++ implementation . After seaching for a while I understood that log4cxx is a part of Apache and decided to use log4cxx.

I have compiled the library as directed even though gathering eveything ant, jre, apr, cppunit took sometime.

Anyhow, I wanted to test the library, honestly for 2 days I have not been able to compile even simple examples. I receive zillions of errors that I provided in the end of the mail. I suspect that I may be missing to include some compilation flags. I used the qt qmake tool to generate a makefile as I am eventually use this tool with qt library.

In my test example I have only one file main.cpp which I have stolen form trivial.cpp (I have only changed the name of the trivial.cpp)


I've seen the dll-interface warnings and the dominance warnings before, but I do not know of any problem they cause. The no imports warnings are due to linking with libraries that are not used which again should cause any problems.

My guess is that the EXE has a dependency on a DLL that is not on the path or in the current working directory and the application never is started. If you linked with a shared build of log4cxx, do you have log4cxx.dll on the path or in the current working directory?

The depends tool should show the DLL dependencies of an application and will show in red any that are not resolved. I'm not sure where it is located in MS VS.NET 7.1, it is located in the Tools menu of the VC 6 and the Platform SDK menus.

If that doesn't change things, could you fire up the application in the debugger and see what happens?

Reply via email to