LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to use external compiler support in CVI 2009 with VC++ 2005

Solved!
Go to solution

The compiler gives me this error message:

 

cvisupp.lib(setprec.obj) : fatal error LNK1103: debugging information corrupt; recompile module

0 Kudos
Message 1 of 8
(4,570 Views)

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

0 Kudos
Message 2 of 8
(4,552 Views)
I just tried creating an empty project from the CVI Wizard in VC++ 2005, it already links to cvisupp.lib. It doesn't build in debug mode, but does build in release mode. In 9.0.1 I was able to link in debug mode, and in fact I need this. When I remove cvisupp.lib from the linker inputs, the linker complains about missing "_CloseCVIRTE@0" as well as "_InitCVIRTEEx@12". I wonder how you can use the CVIRT when you don't link cvisupp.lib.
0 Kudos
Message 3 of 8
(4,541 Views)

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

0 Kudos
Message 4 of 8
(4,524 Views)
I am building from Visual Studio, but not in release mode. I need to be able to debug the code, and this has worked without a problem with 9.0.1.
0 Kudos
Message 5 of 8
(4,505 Views)
Also, initcls.obj is in cvisupp.lib, so you are linking to it, even if you don't do it explicitly.
0 Kudos
Message 6 of 8
(4,504 Views)
Solution
Accepted by topic author DerAgo

I think you're running into this issue. If you install the Visual Studio 2005 SP1 it should take care of the problem.

 

Luis

Message 7 of 8
(4,478 Views)

 

 Although I already had SP1 installed, installing the hotfix from the link solved the issue. Thank you very much!

0 Kudos
Message 8 of 8
(4,454 Views)