LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

problem importing all functions from a DLL file


tinpham wrote:

 

By the way, how were you able to get the call library without the header file?

 


A header file is not strictly necessary to create a VI that uses the Call Library Node to call a shared library (DLL) function. A documentation can be enough and in fact is absolutely required since a header file (unless containing the entire documentation in comments) is normally not sufficient to describe all aspects of calling a function.

 

A header file is helpful since it contains quite a few informations but not nearly enough to make a 100% crash safe caller and in case of LabVIEW it can be used as input to the import library wizard, which takes care of quite a bit of the manual work of creating VIs and setting up a Call Library Node to call the functions in a shared library. But once the import library wizard has done its work you have to go through each VI and using the documentation make sure things like buffer allocations are properly taken care of and that is manual work no matter how smart the import library wizard is made, since it isn't described in the C syntax in any way.

Rolf Kalbermatter  My Blog
DEMO, Electronic and Mechanical Support department, room 36.LB00.390
0 Kudos
Message 11 of 12
(576 Views)

tinpham

I have all the dlls and the header files. All you have to tell me what sequence you called

the functions inside labview. Instead of posting it in here just we will exchange our e-mail

and then exchange whatever ideas we have on this. Since we both have to address same

issues. Let me know what you think about it. you can e-mail me at

yeshwanth.kadire@gmail.com and we will talk.

 

 

Yesh 

0 Kudos
Message 12 of 12
(563 Views)