Discussion:
missing debugging information for referencing module
(too old to reply)
FrankNatoli
2008-01-30 03:10:22 UTC
Permalink
Linking VS2005 MFC application with Intel IPP libraries, for which I
have tweaked the Intel Makefile to specify /ZI and /Od, and have
suddenly started observing:

mpeg4_dec.lib(mp4decvop.obj) : warning LNK4204: 'c:\...
\AtsPlaybackMpeg4\Debug\vc80.pdb' is missing debugging information for
referencing module; linking object as if no debug info

For every Intel IPP library. Was not getting this message but
something has changed. The log file for the Intel IPP library compile
clearly indicates that /ZI and /Od are both in force. Yet whether I am
compiling Release or Debug under VS2005, a flood of the above messages
occurs.

Have deleted the entire Release and Debug directories, no help.

Have removed the NCB file, no help.

Have recompiled the Intel IPP libraries, no help.

Have rebuilt solution, no help.

Exactly what is the linker saying? That my MFC application is not
compiled with /ZI and /Od? That the library, e.g., mpeg4_dec.lib, is
not compiled with /ZI and /Od? Have seen many references to this error
on the web, but no suggestion has helped. Thanks.
FrankNatoli
2008-01-30 03:12:38 UTC
Permalink
Please also note that the linker message is not simply an annoyance. I
really want to debug into the Intel IPP libraries and cannot. F11
simply skips over calls into the Intel IPP libraries. Must find
solution. Thanks.
FrankNatoli
2008-01-30 14:52:12 UTC
Permalink
Problem solved. I had compiled the Intel IPP library in root directory
"X", most because Intel's build script was hardwired to directory "X".
I then renamed "X" to "Y". Although my own application, linking to the
Intel library in directory "Y" had no trouble finding the LIB files,
the LIB/OBJ files apparently have a fully qualified path to each
other, i.e., to their original location in directory "X" not "Y". Once
I renamed "Y" back to "X", the "missing debugging information for
referencing module; linking object as if no debug info" message no
longer appeared.

Loading...