LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

errors creating import library BORLAND LabWindows CVI

Instead of lines of the form:

 

    #define ERR_SUCCESS = 0;

you really should use:

 

    #define ERR_SUCCESS 0

 

The '=' and the ';' are incorrect in your statements. Just remember that a #define effectively introduces a text substitution for the compiler during pre-processing.

 

JR

0 Kudos
Message 11 of 13
(845 Views)

Line 363 of the include file recitates

DLL_API int __stdcall AVS_Init

where DDL_API is defined as

#define DLL_API extern "C" __declspec (dllexport)

As far as I can see the problem is in that extern "C" keyword which CVI cannot handle. As an example, look at some standard CVI include file like utility.h, where that keyword is not included.

 

Are you sure that DLL can be interfaced with C language?



Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
0 Kudos
Message 12 of 13
(831 Views)

Hello,

 

I am having a similiar problem now... Could you in fact attach the dll file?

 

Thanks,

0 Kudos
Message 13 of 13
(688 Views)