05-27-2019 02:33 AM
Hello, I built an executable file of a LabVIEW-project that reads in a camera. If I run the .exe on a computer with LabVIEW installed on it, it works.
However, if I run it on a computer with no LabVIEW installed, the .exe runs but doesn't connect the camera.
In the dependencies of my LabVIEW-project there is the vi.lib and three other .dll files (see appendix). Can that be the reason that it doesn't work on computers with no LabVIEW installed?
How could I include these dependecies into my executable file?
Thank you
Lauro Müller
05-27-2019 03:32 AM
05-27-2019 04:15 AM
I did that but there is still the same problem. Besides, I can't see that the 'vi.lib' file is included in the my installer. Does the 'my installer' automatically add all the dependencies of the .exe?
05-27-2019 04:31 AM
It adds all static dependencies. You will have to add any dynamic dependencies yourself.
In the installer build specification, under "additional installers" if you select to "automatically select recommended installers", you also get included what LabVIEW can detect that is needed. If you have a third party driver, you need to install that separately.
05-27-2019 04:33 AM
05-27-2019 05:57 AM
Vision requires a runtime license on the target, if memory serves.
/Y
05-28-2019 02:43 AM
But how can I add dynamic dependencies?
05-28-2019 03:11 AM
05-28-2019 06:49 AM
But then it creates a folder next to the .exe with the libraries in it, instead of including them into the .exe.
When I want to run this .exe on a computer with no LabVIEW, it cannot read these files if they're not included in the .exe, right?
In the source file settings I should be able to select the destination: Calibration_Femto_3.exe (see appendix), but I'm not.
05-28-2019 07:03 AM
I haven't used llb's since... a long time ago so I'm not sure but guess they cannot be added directly to an exe. But the exe can reference files outside the exe, no worries.
But I'm a little concerned with the dlls, have you added them to the library yourself? These look like dlls that should come from an installer and things might go wrong if you try to override that.