Also, when I compile even the non-debug version of the OS, I get errors like:

BUILD: [01:0000000342:WARNN ] kitl_stub.obj : warning LNK4204: 'c:\wince500\platform\loce\target\armv4i\retail\kern.pdb' is missing debugging information for referencing module; linking object as if no debug info
BUILD: [01:0000000445:WARNN ] ceddk.obj : warning LNK4204: 'c:\wince500\platform\loce\target\armv4i\retail\ceddk.pdb' is missing debugging information for referencing module; linking object as if no debug info


Where has all of this debugging information disappeared to?

Hi Bruce,

This is from the release notes for Service Pack 4 for eVC++:

5.14 Warning LNK4209: debugging information corrupt; recompile module; linking object as if no debug info" when build project for Windows CE 5.0

Install the Windows CE 5.0 Universal SDK and create a Windows CE Applications using eVC 4.0 SP4. The following warning is displayed

"warning LNK4209: debugging information corrupt; recompile module; linking object as if no debug info"

This is a known issue and no workaround is available at the time of releasing SP4.

This is from "Help" in eVC++:

LNK4204

"filename" is missing debugging information for referencing module;
linking object as if no debug info

The .pdb file has an erroneous signature. The linker will continue to link the object without debug information. You may want to recompile the object file using the /Zi option.

Under Platform | Settings are you linking to the correct libraries?

Thanks,

The LNK4204 error I was receiving in Platform Builder. You asked:

Under Platform | Settings are you linking to the correct libraries?

I looked under Platform | Settings, and I didn't see libraries to link to - is there something I didn't see?

Bruce,

From the subject I was under the impression that you were seeing LNK 4204 in eVC++, however the definition for the error is the same in Platform Builder as well.

It appears that some of the .obj files in the BSP from Logic don't have debug options compiled in. For example, ceddk has this problem. Most of the OAL does seem to have debug information; just a few modules don't. Any chance of the non-debug compiled versions having debug versions available?

Can you be more specific about which areas you're looking at?

Trying to create a debug version of the 404 in platform builder. It compiles, but gives warnings that some of the BSP provided object modules are not compiled for debug. For example, ceddk.obj is one.

This is a pretty deep module, and maybe shouldn't be created with debug information. But if so, I wonder if there is a way to create a version with no debug functions internally but that at least is compiled for debug so the linking function works without warnings.

BUILD: [00:0000000626:PROGC ] Linking \WINCE500\PLATFORM\LoCE\src\kernel\kernkitl\ directory.
BUILD: [01:0000000634:PROGC ] Linking C:\WINCE500\platform\LoCE\target\ARMV4I\debug\kernkitl.exe
BUILD: [00:0000000654:PROGC ] Linking \WINCE500\PLATFORM\LoCE\src\kernel\kernkitlprof\ directory.
BUILD: [01:0000000662:PROGC ] Linking C:\WINCE500\platform\LoCE\target\ARMV4I\debug\kernkitlprof.exe
BUILD: [00:0000000682:PROGC ] Linking \WINCE500\PLATFORM\LoCE\src\drivers\ceddk\dll\ directory.
BUILD: [01:0000000690:PROGC ] Linking C:\WINCE500\platform\LoCE\target\ARMV4I\debug\ceddk.dll
BUILD: [01:0000000709:WARNN ] ceddk.obj : warning LNK4204: 'c:\wince500\platform\loce\target\armv4i\debug\ceddk.pdb' is missing debugging information for referencing module; linking object as if no debug info