LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Question on "generate dll import library" in CVI 8.5.0

I'm using the "Options>>Generate DLL Import Library" menu tool on a vendor supplied DLL (because I can't use their MSVC6 LIB file that they supplied inside of CVI 8.5.0, for some unknown reason).  I'm doing this from an empty CVI 8.5 project environment (cvi.exe -newproject).  In the header file that they supplied with the DLL, I only had to add the line    #include <windows.h>   because CVI could not identify DWORD.
 
When I ran this tool, it created the LIB file, which works fine to link to the DLL at the launch of the EXE, and runs the necessary functions properly, but when it created the LIB file, I got lots of waring messages (see attached image below).  It is obvious to me that these messages are related to CVI and not my vendor supplied DLL, but do I have something configured incorrectly in CVI that is causing this to happen...?
 
 
--
To whom it may concern: My alias is also my nickname, I've had it since I was a (very) skinny basketball-playing teen. OK, so I've got a 38 inch waist now, but my hometown friends haven't shaken that appellation for me. I trust that you will someday be OK with that alias, as I have been with that nickname.
0 Kudos
Message 1 of 2
(3,178 Views)
The behaviour is allright.
Once you include windows.h to that header file, all of the funtion prototypes in windows.h are checked for presence in the DLL. And as many are not, you get the warnings. (Lucky we are: CVI only mentions up to 100 warnings.)

To circumvent the warnings, you could manually define DWORD instead of including windows.h. This will make the warnings disappear.

Regards, Guenter
0 Kudos
Message 2 of 2
(3,153 Views)