09-14-2018 06:19 AM
I am using LV2015, windows 10.
I made a simple program that uses a lvlib (installed via VIPM) that is located in vi.lib folder.
I have application builder, and did the build for exe.
My questions are:
Solved! Go to Solution.
09-14-2018 07:01 AM
As long as things are not dynamically called, they will be included in the executable. For those that are dynamically called, you need to include it in your project and then you can "always include" in your executable in the build specification.
09-14-2018 07:12 AM
thanks,
I have found the dialog box with the setting:
If I set the destination to support directory, I get all the classes/files of the lvlib inside support folder ("data" by default), and that's not convenient....
09-14-2018 07:18 AM
Where you really want to go is in the Source Files section. In there is where you can force a library/VI to be "Always Included".
02-14-2019 03:34 AM
Same issue here, with a zip file.
The dependencies are't listed under source files, so I've moved them in the project explorer, all good. But it won't let me move the vi.lib, and it isn't listed under source files in the build spec.
02-15-2019 10:48 AM
What happens when you try to run the executable on another computer with the run time engine?
02-15-2019 11:55 AM
Not sure. I'm creating a zip file, not an executable.
I've had no problems with exe's.