Labwindows CVI 2010 and GetProcessAddress()

Question

I am using Labwindows CVI 2010 v10.0.1 after upgrading from version CVI 2010 v10.0.0. After the upgrade, I have a compile error from a statement that compiles just fine in the previous version. The error is:
"Operands of = have illegal types 'pointer to __stdcall int function(int,pointer to char,pointer to char,pointer to char,int,pointer to char,pointer to char)' and 'FARPROC'."
What causes this error is the following statement in the code:
my_FP = GetProcAddress(dll_handle, "DLL_FUNCT");
and the definition of my_FP is:
int __stdcall (*my_FP)(int x, char y[], char z[], char *m, int g, char A[], char B[]);
(function names and parameters have been changed for simplicity)
As I said, this line compiles just fine in 10.0.0, but not in 10.0.1. Is there a specific update to the compiler that will cause this error? What can be done to fix this?
Thank you very much for your time and help.
Solved!
Go to Solution.

Answer 1

You're correct. This was caused by a change in CVI Windows SDK headers that took place in version 2010 SP1. The change was associated with bug fix #275934. Unfortunately, this bug fix introduced this undesirable side effect of requiring a cast for any function that returns a FARPROC function poinrter (such as GetProcAddress). Upon further reflection, this side effect is unacceptable, and needs to be corrected in the next release. This is being tracked internally with bug ID #336341.
I'm really sorry for this inconvenience. Until the problem is resolved, using the typedef & cast solution that you already implemented is a valid workaround.
An alternative workaround, in case you're worried about other projects, or other functions, where this error might also pop up, is to edit CVI2010\sdk\include\windef.h and replace the following FARPROC definitions (in lines 226 and 230, respectively):
typedef INT_PTR (FAR WINAPI *FARPROC)(void);
typedef int (FAR WINAPI *FARPROC)(void);
with:
typedef INT_PTR (FAR WINAPI *FARPROC)();
typedef int (FAR WINAPI *FARPROC)();
Doing this will avoid the problem throughout a given installation of CVI.
Luis
NI