02-17-2012 03:49 AM
Solved! Go to Solution.
02-21-2012 10:37 AM
Hello IEE_newsoft,
Looking at the screenshot you posted, one recommendation is to make sure the header file and library have the same name, also have you been able to call the dll or lib successfully in another environment ie like visual studio to verify there is nothing wrong with the files. Also look at this Developers Zone,http://zone.ni.com/devzone/cda/tut/p/id/3453 it walks you through how to use a third party dll in CVI, and http://zone.ni.com/devzone/cda/tut/p/id/8503 shows you how you can use either Dynamic or Static linking to call your dll.
Hope this helps
02-23-2012 02:00 AM
Hi,
I finally found the reason and the solution for my problem. The reason was the fact that CVI is set to Borland compatibility mode while the UL library from MCC was compiled with a Microsoft compiler. After setting CVI to Microsoft compatibility, I was able to build and run my test application.
As I need Borland mode to stay compatible with the parental application where I want to implement the MCC board, I found a very useful hint on the NI forum that describes how to create an import library:
http://digital.ni.com/public.nsf/allkb/EBCE04F31CBB9ACE862569290071CB28 ("Creating Import Libraries for a DLL in LabWindows/CVI")
This solved my problem
Nevertheless, thank you fro supporting
Regards
12-02-2015 11:45 AM
If you are using Borland C comptibility you can use the library provided by MCC named cbw32bc.lib instead of cbw32.lib