Original Post
When I try to compile my project for DEBUG (OK for RETAIL), I get the following message...
dinput8.lib(dilib2.obj) : fatal error LNK1103: debugging information corrupt; recompile module
Error executing link.exe.
Linker Tools Error LNK1103
debugging information corrupt; recompile module
Possible cause
The compilation was terminated before a valid object file was created.
Recompile the given object file. If recompiling does not correct the problem,
note the circumstances of the error, try to isolate the problem, and create a
reproducible test case. Then consult the technical-support help file, the
technical-support section in one of your manuals, or Microsoft Product Support
Services.
See Corrupt Object File for more information.
Corrupt Object File
Sometimes the linker is unable to process your object files because they are
corrupt. Besides the usual causes of corrupt files such as network problems or
exposing a floppy disk to a magnetic field, sometimes the compiler writes an
incorrect object file, which you should report to Microsoft Product Support
Services.
After you have ruled out a hardware, operating system, or network problem as
the cause of the corrupt object file, you should try the tips below. Changing
compiler options and recompiling sometimes causes the compiler to write a non-corrupt
object file.
Possible solutions
Turn off optimization with the /Od (Disable) option.
Disable minimal rebuild with the /Gm– (Enable Minimal Rebuild) option.
Compile with the /Gy (Enable Function-Level Linking) option to package functions.
Use a different code generation option. See the /G (Optimize for Processor) options.
Change the order of functions and global variables