LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Built .exe file missing ctl files

Solved!
Go to solution

Hello

I have run into a strange problem. I am building a exe file to run my application on a non development machine. It builds and i can start it on my development machine without any problems.

 

When moving it onto another machine, it searches for two ctl files and doesnt find them. The strange thing is that if i just click cancel when asked to find the files, the application starts and runs without any problem. Even if i build the application with the files specifically included and when asked for the files being suggested the very folder where the files are clearly present the application just wont recognize them. But it still starts and works.

 

I am not sure what to do with this, i have tried what i think is most variations of including the files in the build. My client would rather not have to wait for the search and click cancel every time the application is started. If i was missing some drivers on the other machine it shouldnt have started.

 

Its Labview 2016. The controls are type defs, one cluster and one enum. They are used with shared variables (single process) if that makes any difference.

 

Anyone have any idea or suggestion?

 

Best Regards,

Nimgaard

0 Kudos
Message 1 of 6
(4,605 Views)
Maybe that helps:
Under the build properties of your exe, goto "Additional Exclusions" and select "Disconnect type definitions".

Regards, Jens
Kudos are welcome...
0 Kudos
Message 2 of 6
(4,601 Views)

Thanks for the answer, i tried this but then it wont build. 

 

Error:

Error 1502 occurred at AB_Source_VI.lvclass:Close_Reference.vi -> AB_Build.lvclass:Save.vi

Possible reason(s):

LabVIEW: Cannot save a bad VI without its block diagram.

 

Clicking out it works again.

0 Kudos
Message 3 of 6
(4,596 Views)
Solution
Accepted by topic author Nimgaard
That's surprising to me. Never had problems with activating that option - in my experience it helps esp. to resolve problems with real-time executables. On the other hand, I'm avoiding shared variables as much as I can so that's probably the reason for your problems. You could check that easily by removing the type definitions from your shared variables.

Regards, Jens
Kudos are welcome...
Message 4 of 6
(4,585 Views)

That actually helped. Disconnected the type defs and it built. Built ok and started without asking for the controls.

 

Thank you very much for the fast answer, even managed to fix it before leaving my client.

 

Best Regards,

Nimgaard

0 Kudos
Message 5 of 6
(4,580 Views)

Disconnecting type defs from shared variables worked for me too  using the disconnect in the build doesn't work because the VIs using the shared variable need to be recompiled to work. Disconnecting them in the project library and reconciling works. I suggest keeping a copy of the project sources before disconnecting.

0 Kudos
Message 6 of 6
(2,414 Views)