Undefined symbol '___CompiledDebuggingLevel' referenced in ..... cvistart.lib

[Dizz]

Hi All,

With one big project I'm working on, which has several static libraries, I'm getting the following error when building in release mode:

Undefined symbol '___CompiledDebuggingLevel' referenced in "c:\program files\national instruments\cvi2012\bin\Msvc\cvistart.lib".
Undefined symbol '___PtrInfoFixupTable' referenced in "c:\program files\national instruments\cvi2012\bin\Msvc\cvistart.lib".

Undefined symbol '___CVI_Sections' referenced in "c:\program files\national instruments\cvi2012\bin\Msvc\cvistart.lib".

Undefined symbol '___UFRNameTable' referenced in "c:\program files\national instruments\cvi2012\bin\Msvc\cvistart.lib".

I have had this problem before, and with the help of the following threads, was able to fix it by recompiling my static libraries.

http://forums.ni.com/t5/LabWindows-CVI/error-Undefined-symbol-CompiledDebuggingLevel-referenced-in-q...

http://forums.ni.com/t5/LabWindows-CVI/Urgent-8-5-1-Link-errors-related-to-cvistart-lib/m-p/720628

http://forums.ni.com/t5/LabWindows-CVI/Problem-with-Shockwave-Flash-ActiveX-control/m-p/720209

http://forums.ni.com/t5/LabWindows-CVI/Errors-in-linking/m-p/203572

http://forums.ni.com/t5/LabWindows-CVI/Link-error-after-including-a-static-library/m-p/2185036

Unfortunately, recompiling, marking for compilation or deleting .cvibuild folders dosent work for me this time around.

I can compile in debug mode with no probs.

I can not compile in release mode, unless all my *.libs are excluded and the corresponding library source *.c files included.

All projects are being built in CVI2012.

Can anyone shed some light on why this link error could be happening?

I'm not too familiar with how the CVI environment operates at this level. I read in one of the other (linked) posts that the functions of those undefined symbols are only used when debugging which adds to my confusion..

cheers,

Diz.

[D-Cubed · Accepted solution]

Hi Diz,

Have you tried the step provided by D_Biel in http://forums.ni.com/t5/LabWindows-CVI/Link-error-after-including-a-static-library/m-p/2185036 ?  It appears that this may be a known issue in LabWindows/CVI 2012, and has a work around.  The error seems to originate from the static libraries built in LabWindows/CVI.  Please try the suggestion below if you have not already.

---

@D_Biel wrote:

Hi CPP,

Are you using CVI 2012? If so, then you likely ran into known issue 372694. This is a bug with the build configuration for the static library introduced in CVI 2012. The problem occurs when you switch the Target Type from a Dynamic Link Library or Executable that was in a debug configuration to Static Library. Static Libraries are not allowed to be built in a debug configuration, so CVI tries to switch from the debug configuration to release when the target type is changed to Static Library. In CVI 2012, this change from debug to release does not fully occur, so you are left in an inconsistent configuration state. In this state, the static library is built with debug symbols that it does not define.

The good news is that it is very easy to fix. After switching the Target Type to Static Library, simply reselect Release as the configuration (the Release option will already be selected, but go ahead and select it again anyway). Once you reselect that, the Static Library will be built correctly without the debug symbols.

Using the Enable .Obj Option should not be necessary, and will not allow you to debug your application.

Edit: This issue will be addressed in the next release of CVI. 

---

Warm Regards,

[Dizz]

Thanks Daniel,

Reselecting release did the trick.

cheers,

Diz.

[JG30100]

Hi,

I have the same problem, but it occurs when i compl in release dynamic dll but it works with debug mode.

Thanks to help me

[JG30100]

An information i am under CVI 2012

[LindsW]

Hi,

It sounds like the issue discussed above has to do with building static libraries.  Is this what you are trying to do, or are you trying to build a dll?  Could you also give more information on what you are trying to compile and post the specific errors you are seeing?

Regards,