LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW 7.1 fundtypes.h

Solved!
Go to solution

I am getting a syntax error when trying to compile an CIN .c-Code

 

"/opt/lv71/cintools/fundtypes.h", line 57: syntax error before or at: typedef 

 

 

Is there anyone who has seen something like this while working with CINs ?

 

Developement-PC: Solaris 10

LabVIEW 7.1 Professional

0 Kudos
Message 1 of 5
(1,301 Views)
Solution
Accepted by topic author musa_

I think I compiled the last CIN about 20 years ago. Before LabVIEW 6.0 CINs were the better way to interface to external code, but with 6.0 and definitely 7.x it is much more useful to compile things into a shared library and use the Call Library Node to interface to it!

 

That said, fundtypes.h line 57 is about defining the basic integer types for LabVIEW when compiling for Unix. There is nothing that would seem to be immediately springing out as possible cause. What Solaris compiler are you using? Do your standard headers also define types like int8? LabVIEW 7.1 was released a bit before Solaris 10, so there is definitely a possibility that the cintools headers don't quite compile neatly with it.

 

 

Rolf Kalbermatter
My Blog
0 Kudos
Message 2 of 5
(1,259 Views)

@rolfk wrote:

What Solaris compiler are you using?


I am using the standard C compiler cc: Sun C 5.11 SunOS_sparc 2010/08/13.

 

 


@rolfk wrote:

Do your standard headers also define types like int8?


This could be the case I will look into that deeper.

 

I already tried to compile and run the VIs in the /opt/lv71/examples/cins/mult/ directory but with no luck. This time I don't get this error message atleast, but when trying to load the mult.lsb file into my CIN it won't work.

 

LabVIEW Error-Msg: 

musa__0-1704355986449.png

 

It stays like this and won't load. I use the tool "lvmkmf" in the /opt/lv71/cintools/ directory to create the "mult.make"-file and the command "make -f mult.make" to create the "mult.lsb"-file, just like described in the LabVIEW documentations.

 

Am I still doing it wrong or are CINs just unusable for LabVIEW 7.1 / Solaris 10 ?

 

I guess my best bet is to write a .dll and use the Call Library Node function.

0 Kudos
Message 3 of 5
(1,225 Views)

@musa_ wrote:

Am I still doing it wrong or are CINs just unusable for LabVIEW 7.1 / Solaris 10 ?

Not sure about Solaris 10 and how much it is different to Solaris 9, which supposedly was supported by LabVIEW 7.1.

 

I guess my best bet is to write a .dll and use the Call Library Node function.


On Solaris this is definitely not a DLL. Not sure what the actual Solaris pendant is. They used to have their own type of fairly buggy shared library format if I'm not mistaken. But that might have been from SunOS days. Later versions of Solaris probably adopted the ld system as had been used by Linux for quite some time already and there the shared library have usually the .so ending.

Rolf Kalbermatter
My Blog
0 Kudos
Message 4 of 5
(1,214 Views)

@rolfk wrote:

@musa_ wrote:

Am I still doing it wrong or are CINs just unusable for LabVIEW 7.1 / Solaris 10 ?

Not sure about Solaris 10 and how much it is different to Solaris 9, which supposedly was supported by LabVIEW 7.1.

 

I guess my best bet is to write a .dll and use the Call Library Node function.


On Solaris this is definitely not a DLL. ... the shared library have usually the .so ending.


My bad that's what I meant.

0 Kudos
Message 5 of 5
(1,208 Views)