|
I think I see what the problem is. Some time ago when I
built logcxx with Visual Studio 6, I built a debug version and a release
version. I set the output file for the debug version to be "log4cxxD.dll", and
the release version to be "log4cxx.dll". This worked fine at the
time.
However, I rebuilt log4cxx using the above mentioned output
files, but the log4cxxD.lib file doesn't appear to be linked to log4cxxD.dll.
It's linked to log4cxx.dll.
S:\projects\ewissp\lib>strings
log4cxxD.lib | grep dll log4cxx.dll/
1136924749
0 494
`
This
is probably a simple thing to do, but does anyone know how to get the output
file for the debug version to be log4cxxD.lib, and have it link to
log4cxxD.dll?
Any
help appreciated.
Chris
I can build and run a simple app in Visual Studio 6.0 wth
log4cxx 0.9.7.
However, if I build and run this app in Visual Studio .NET
I get an access violation as decribed below.
Visual Studio .NET must be doing something
different.
Any ideas?
Thanks,
Chris
From: Combes, Chris M.
[mailto:chris.combes@xxxxxxx] Sent: Tuesday, January 10, 2006 3:02
PM To: Log4CXX User Subject: RE: Mpr.dll Unresolved
Import
I am able to debug log4cxx up until a certain
point:
LoggerRepositoryPtr&
LogManager::getLoggerRepository()
{
...
return
repositorySelector->getLoggerRepository(); <--- GETS TO
HERE
}
I'm unable to step into this
code however. I get the usual "There is no source code available for the current
location." pop-up dialog.
Does anyone know where I get
set a breakpoint for this line?
I set a breakpoint in all
locations where "getLoggerRepository()" is defined, but it doesn't
work.
Any help
appreciated.
Chris
I can debug by stepping into the getLogger call and I get
to a line in xstring:
const_iterator operator--(int) { //
postdecrement const_iterator _Tmp =
*this; <-- CRASHES HERE --*this; return
(_Tmp); }
Chris
Thanks for responding Josh.
When I run my app (I created a separate test app now which
simply logs something), and hit "getLogger"
I get an access violation window.
log4cxx::LoggerPtr m_logger; m_logger =
log4cxx::Logger::getLogger(_T("MyApp"));
Any ideas?
Thanks,
Chris
MPR.dll is delay loaded. You should see an hourglass next to
the red icon for MPR.dll. You shouldn't need it for log4cxx to run.
On 1/10/06, Combes, Chris
M. <chris.combes@xxxxxxx>
wrote:
After
building log4cxx-0.9.8, if I run depends.exe on the resultant log4cxx.dll
file, I get the following error:
Warning: At least one module has an
unresolved import due to a missing export function in a delay-load
dependent module.
MPR.DLL is highlighted in red.
If I link to
log4cxx.dll my app will not work.
I downloaded 0.9.8 from http://littletux.homelinux.org/log4cxx/
Any
help
appreciated.
Thanks, Chris
|