Can not find size_t during import a dll and calling a function crash labview

Question

Hello, experts
I need to use FingerLakeInstrument  DLL ( see the attached) inside Labview to talk to a CCD camera. it is built from microsoft visual studio C++
I unzip FLI dll in my D:\proj\...\linfli-32 and import dll from there. created a c:\FLIDBG.txt as FLI dll needs to write debug message to it if FLISetDebugLevel() or others are called.
During importing the dll, first thing I got is <sys/types.h>  ( ie size_t ) cannot be found. I have installed free version of microsoft visual studio C++
but can not find "typedef unsigned int size_t"
at the end, I just added
 typedef unsigned int size_t;
in the libfli.h. Having done that, I am able to import all functions into Labview and have a user library called libfli.
However, as soon as I start calling a simple function in a test.vi, such as FLIGetLibVersion(char* ver, size_t len), which involves nothing other than the library, the labview will crash.
I created a simple C test.exe which calls many functions without any problem
any suggstion?
regards
xiaofeng
Solved!
Go to Solution.
Attachments:
libfli-32.zip ‏93 KB

Answer 1

Hi, Smercurio_fc
thanks for your reply. Yes, you are pointing to the right place.  I have solved the crash problem.
when importing DLL into Labview using Tools\import\Shared Library (.dll), Labview automatically set the calling convention as C not as stdcall (WINAPI).  it is this that later the labview crashes when a function is called.  as soon as I manually re-selecte calling convention as stdcall, my test.vi works OK (see attached).
I tried Call Library Function too to call libfli.dll, as long as I select stdcall as call convetion. the test.vi works.
How do I know which Call convention I need to choose if  there is no infomation from DLL provider?
as for the size_t,
I add   #include <crtdefs.h> in libfli.h and 
 add additional include path as
C:\Program Files\Microsoft Visual Studio 10.0\VC\include.  this  solved the "not found" issue.
for this case I know that the DLL is built from VC++,  is this right way? 
again, thanks for your time.
xiaofeng
Attachments:
test.vi ‏13 KB