LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

CIN and MS Visual C++ 5.0

Hello all,
is Microsoft's Developer Studio 97 Visual C ++ 5.0 acceptable compiler
for
crating CINs?
If not can someone suggest a C compiler that is ?(I am using Win NT
SP5).
I did (or at least I think I did) everything by the book: placed CIN on
the
diagram, connected input and output, did 'create .c file', and inserted
the
code. I configured Visual C++ 5.0 compiler as in CIN Ref. Manual,
however
can not get *.lsb file. Compiler states that *.c file compiles without
problem. I tried compiling and building whole 'project' but to no avail
for
*.lsb file. I am not sure if I perhaps entered wrong paths in the
project
input fields ( I tried playing around with them, even changing to DOS
names).
Again, I am not sure if I
am doing something wrong or this compiler is
not
'compatible' with LV.
Here is the snippet of the error code I got when tried to build the
project:

--------------------Configuration: cinwork - 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
Creating library Debug/cinwork.lib and object Debug/cinwork.exp
Performing Custom Build Step
The name specified is not recognized as an
internal or external command, operable program or batch file.
Error executing c:\winnt\system32\cmd.exe.

cinwork.dll - 1 error(s), 3 warning(s)

Thanks


Sen
t via Deja.com http://www.deja.com/
Before you buy.
0 Kudos
Message 1 of 2
(2,459 Views)
Hi all,
I figured out the problem for my own question. so if anyone is
interested here it is:
In CIN Ref. manual, which comes in the *.pdf format on the disk NI
people made a mistake (typo) and an (to me very important) omission

mistake typo for Visual C++ IDE p 1-30 under Build commands:
manual: \win32\lvsbutil $(TargetName) -d
$(WkspDir)\$(OutDir)
should be: \win32\lvsbutil $(TargetName) -
d "$(WkspDir)\$(OutDir)"
Note parentheses around $(WkspDir)\$(OutDir)

omission is that they did not emphasised, in the *pdf file but did on
the web page, that path names should be in the dos format.

after implementing correct paths I got everything to work correctly
igor


In article <8kih35$sm$1@nnrp1.deja.com>,
igor@korugaindustries.com wrote:
> Hello all,
> is Microsoft's Developer Studio 97 Visual C ++ 5.0 acceptable
compiler
> for
> crating CINs?
> If not can someone suggest a C compiler that is ?(I am using Win NT
> SP5).
> I did (or at least I think I did) everything by the book: placed CIN
on
> the
> diagram, connected input and output, did 'create .c file', and
inserted
> the
> code. I configured Visual C++ 5.0 compiler as in CIN Ref. Manual,
> however
> can not get *.lsb file. Compiler states that *.c file compiles
without
> problem. I tried compiling and building whole 'project' but to no
avail
> for
> *.lsb file. I am not sure if I perhaps entered wrong paths in the
> project
> input fields ( I tried playing around with them, even changing to DOS
> names).
> Again, I am not sure if I am doing something wrong or this compiler
is
> not
> 'compatible' with LV.
> Here is the snippet of the error code I got when tried to build the
> project:
>
> --------------------Configuration: cinwork - 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
> Creating library Debug/cinwork.lib and object Debug/cinwork.exp
> Performing Custom Build Step
> The name specified is not recognized as an
> internal or external command, operable program or batch file.
> Error executing c:\winnt\system32\cmd.exe.
>
> cinwork.dll - 1 error(s), 3 warning(s)
>
> Thanks
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
>


Sent via Deja.com http://www.deja.com/
Before you buy.
Message 2 of 2
(2,459 Views)