views:

80

answers:

1

how can it be that a dll that i build here (in debug mode) tries to load msvcr80.dll and msvcr80d.dll ... i assume this leads then to a conflict as it can resolve the same symbols twice ...

i have no idea why the dependency to msvcr80.dll comes in. according to dependency walker ouput the dependency comes directly from my dll and not via another dll ...

could this be a problem of build settings of my debug build?

+1  A: 

It may be caused by one of the dlls you are liked with is linked in release mode so they load msvcr80.dll while you are loading msvcr80d.dll.

And yes, this may cause a problem

could this be a problem of build settings of my debug build?

Yes

Artyom