09-27-2013 07:02 PM
I'm using LV Connection VIs to detemine mouse poition. When the executable runs, the user is promted to find the shared library lvinput.dll. It shows up under dependencies in the project, and even if I explicitily include this dll in the build, the problem persists. What might I be doing wrong?
09-30-2013 08:28 AM
Here are a few things to consider:
1) If you are running the executable on a separate computer, it is important that the version of the LabVIEW Run-Time Engine on the target computer is the same as the version of LabVIEW that executable was built in. If you need to get the Run-Time Engine, see ni.com/downloads.
2) When including libraries in the build, the library should be under "My Computer" in the project instead of Dependencies. In Application Properties, choose the category "Source Files" and add the library to the "Always Included" section.
3) This link has useful tips on how to call DLLs in Stand-Alone Executables: Why Can My Stand-Alone Executable Not Find My DLL, Even Though I Have Specified the Path for the DLL...
Are you getting error codes? If yes, then please write it in the post or include a screenshot.
09-30-2013 11:57 AM - edited 09-30-2013 12:22 PM
Thank you for the information. I realized that I did not copy the new support files folder for the exe to the target machine. Moreover, it looks like the applicaiton builder automatically copies the dll to the support folder, no need to include it explicitly. Bravo!