11-02-2018 05:36 AM
Hello
I have updated a test application for a device we are producing from LV2013 to LV2017. Now I have trouble, to generate the EXE-file.
The test application contains a packed library, that does the communication over Ethernet with our device with help of a UDP connection. All is working fine in the LV2017 development environment, I could operate all functions of our device with the help of the test VI. Then I generated an exe-file with help of the application builder, and the application does not work. It shows the corrupted arrow, like a VI that does not work. I got also the notice, that a VI is not working, and I need the LV development system to eliminate the error.
Inside the development environment all VI's show no errors, I tried to play with the settings inside the application builder - always the same result, a non operating exe-file.
I also tried it out with LV2018 - same result. The exe-file does not work. I did also a mass compile of all the VI's before the build with no errors.
Does somebody have any idea, where I can start to look what is faulty here? Curently I can operate the
Operating system is Windows 7.
11-02-2018 06:25 AM
Hi,
maybe a vi is pointing or call an object outside your project directory.
to eliminate this make a save project as and rename it to be sure
11-02-2018 07:02 AM
Hi Simo22,
I tried this out, by putting a copy of the project folder on my laptop, that has no access to the original folder ant there the same problem. Thanks for your hint.
11-02-2018 09:02 AM
Typically, when an program works in the DEV environment but doesn't work as an EXE, it's often a missing dependency. Did you try to Always Include the library file?
11-12-2018 10:26 AM
Hallo,
if you mean the settings for the source files, then: yes, I always included packed library in the build.
I have tried to build it local on my PC as well, as build it on a network place, always the same result exe-file does not work.
Today I tried to exclude parts of the structure, to see if it could be related to the code, and I set up a new build for the exe file - no result, all not working exe-files.
has anybody an Idea, where to search also for possible reasons that the program does not run after the build? I'm a bit helpless now, tried so many thinks ...
Kind regards
Guido
11-12-2018 10:54 AM
My thoughts are going to the PPL. If things are not exactly where it expects, bad things can happen. Does the PPL depend on any other PPL?
11-12-2018 11:06 AM
Post a picture of the error. Does it popup with a dialog where it's looking for a certain file? Or does it simply startup with a broken arrow? Does your application use a .dll file and if so, is the application able to find it?
I've seen suggestions of:
11-13-2018 01:54 AM
Hello thanks for the reply,
Guido