03-25-2010 07:28 AM
The compiler gives me this error message:
cvisupp.lib(setprec.obj) : fatal error LNK1103: debugging information corrupt; recompile module
Solved! Go to Solution.
03-25-2010 03:10 PM
I am able to use the VCPP 2005 compiler all OK from LabWindows 2009.
I do not get any link errors, though I do get quite a few warnings, most of them coming from CVI header files (un named structs for example).
The external compiler is supported in release mode only - I don't think any debugging info should be involved.
It seems that maybe one of the NI object modules (cvisupp.lib) has something in it that was compiled in debug mode rather than release mode.
Looking at a map of my project, it does not link cvisupp.lib.
Menchar
03-26-2010 01:28 AM
03-26-2010 12:56 PM
Well, I do call InitCVIRTE in my main, but it doesn't find it in cvisupp.lib, it finds _InitCVIRTEEx@12 this way:
00404808 _InitCVIRTE@4 initcls.obj
00404818 _InitCVIRTEEx@12 initcls.obj
004048FC _CloseCVIRTE@0 initcls.obj
The identifier cvisupp.lib is no where in the map of my project.
I do see this library in the NI folders on the PC however.
I think we may be crossed up here in what we're doing - I am building the application from the LabWindows 2009 framework in release mode using the VCPP 2005 compiler as an external compiler ... are you building from Visual Studio or from CVI 2009?
Menchar
03-29-2010 12:36 AM
03-29-2010 12:38 AM
03-30-2010 10:18 AM
I think you're running into this issue. If you install the Visual Studio 2005 SP1 it should take care of the problem.
Luis
03-31-2010 12:48 AM
Although I already had SP1 installed, installing the hotfix from the link solved the issue. Thank you very much!