I am building a .dll with Visual C++ .NET 2003.
That dll is called within my .vi by a Call Function Node.
When I open that .vi from Labview no pb with the .vi it loads the .dll.
When I try to debug that .dll (by setting labview.exe as an external process to run for my dll project, and then load up the .vi in labview that calls it) I get an error message "No DLLs were found in the waterfall procedure" as soon as I open my .vi.
For information that .dll of mine is linked to IPP (Intel® Integrated
Performance Primitives) .dlls for which I have the path set in the Windows PATH environment variable.
Thanx in advance for your help.
can you run your dll in a vi? do you get this error only when you running the dll in a SubVI ? Maybe you can post your code here..
> can you run your dll in a vi?
Yes, I can run the .vi containg the Call Function Node that calls a function of my .dll but I have bug in that .dll. I am trying to find that bug that's why I open the .vi by starting labview.exe as an external process from Visual C++ .NET 2003.
> do you get this error only when you running the dll in a SubVI ?
I don't use any sub .vi
> Maybe you can post your code here..
Do you mean the Labview code and/or the C++ code of the .dll?
As I mentioned, my .dll is calling some IPP (Intel® Integrated Performance Primitives) functions so you would have to have IPP to run it.
thx for your help,
Here is my Labview code calling functions of my .dll.
Thx for your help,
Hi Jean Philipe,
you can't debug non LV dlls in LV. For that the dll has to be always compiled as debuggable. I don't know if you have this option in the precomiled Intel dlls.
> you can't debug non LV dlls in LV.
I don't get what you mean here by a LV dll versus a non LV dll.
The .dll I wrote is just a simple wrapper enabling me to call IPP functions.
> For that the dll has to be always compiled as debuggable. I don't know if you have this option in the precomiled Intel dlls.
I compiled my .dll in debug mode but of course the intel .dll doesn't come along with debug information. Actually I don't want to debug the intel .dll but the code I wrote around the intel function calls.