Link to home
Start Free TrialLog in
Avatar of trochel
trochelFlag for United States of America

asked on

VS 2005 linked against WinDDK static library

Hello
I just created a static library in WinDDK and linked into an application in VS2005.    It compiles and links and the application runs.   The problem is the statis library did not contain debug information so I get a LNK1103: debugging information corrupt; recompile module on the static library.  does the static library contain debug information or can it be built to do so OR can I build the application for debug excluding the need for debug info in the static library?
Thanks in advance for your reply
SOLUTION
Avatar of jkr
jkr
Flag of Germany image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of trochel

ASKER

It only provides this error in a Debug build.   When I build for Release, the application runs, but I cannot debug to resolve other errors
I understand that, but as I mentioned, this is most unlikely to cause this error (you're usually able to link any release library with a debug build, most 3rd party vendors don't even provide debug versions). Again, can you try to check the library's integrity with 'lib.exe' and 'dumpbin.exe'?
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of trochel

ASKER

I deviated from the static library approach because the response provided enough information to confirm that I was experiencing problems that were outside of the norm.   My alternate approach worked and all is well!!