LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Query for CIN

Hi everyone,

I want to convert existing C++ code to VI. so I have tried to make it by
using CIN(Code Interface Node). But The manual with shipped from NI is not
complete to understand.

I have compiled them in Visual C++ 6.0 IDE. When comping, there are no
errors. But linking there are lots of warnings and errors as follow.
--------------------
--------------------Configuration: cin for labview - Win32
Debug--------------------
Linking...
...\..\..\National Instruments\LabVIEW\CINTOOLS\win32\lvsbmain.def : warning
LNK4017: EXETYPE statement not supported for the target platform; ignored
...\..\..\National Instruments\LabVIEW\CINTOOLS\win32\lvsbmain.def : warning
LNK4017: SUBSYSTEM statement not supported for the target platform; ignored

...\..\..\National Instruments\LabVIEW\CINTOOLS\win32\lvsbmain.def : warning
LNK4017: STUB statement not supported for the target platform; ignored
...\..\..\National Instruments\LabVIEW\CINTOOLS\win32\lvsbmain.def : warning
LNK4017: CODE statement not supported for the target platform; ignored
...\..\..\National Instruments\LabVIEW\CINTOOLS\win32\lvsbmain.def : warning
LNK4017: DATA statement not supported for the target platform; ignored
Creating library Debug/cin for labview.lib and object Debug/cin for
labview.exp
cin.obj : error LNK2001: unresolved external symbol _CINRun
Debug/cin for labview.dll : fatal error LNK1120: 1 unresolved externals
Error executing link.exe.

cin for labview.dll - 2 error(s), 5 warning(s)

-----------------------------------------------

I have made project for CIN and set up project setting propery that appear
in CIM manual.

I need the way to solve this problems and I hope that detail document for
CIN.

Thanks
0 Kudos
Message 1 of 2
(2,826 Views)
If you are using the July 2000 manual "Using External Code in LabVIEW," then the instructions are correct for the IDE except for the "win32\" directory inclusion on page 3-14. This is not correct for LabVIEW 6. Just remove the "win32\" in the directory path and everything should work fine.
0 Kudos
Message 2 of 2
(2,826 Views)