05-19-2007 02:20 AM
05-19-2007 08:45 AM - edited 05-19-2007 08:45 AM
Hi tisiman,
There are two ways of linking a DLL in LabWindows/CVI:
- Static linking (linking implicitly): In this case, the DLL will be
loaded into memory when the application is loaded. This method uses the header
file and import library of the DLL. You will include the import library in your
CVI project.
- Dynamic linking (linking explicitly): In this case, the DLL will
be loaded into memory when the user says so by using the LoadLibrary and GetProcAddress
Windows SDK functions. This is explained in the How
Can I Access DLL Functions in a LabWindows/CVI Program Without Including the
Import Library in t... KnowledgeBase.
In your case, dynamic linking is the approach you want to take.
With static linking, function calls will be resolved during link time by CVI
and if it can't find the appropriate symbol, it will provide that "symbol
not found" error.
The above information is discussed in the Linking
to Functions Defined in a DLL From LabWindows/CVI KnowledgeBase and the FAQ: Using Dynamic Link
Libraries with LabWindows/CVI tutorial.
Hope this helps!
Best Regards,
Message Edited by Jonathan N on 05-19-2007 08:45 AM