LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

stand-alone application build requirements in LV 7.1

I have a working program that I would like to convert as stand-alone application. I know that I need RTE 7.1 on the target computer only to make it work (I use LabVIEW 7.1 Professional Dev Env).

 

To build the stand-alone application I used "Build app or shared DLL" in "Tools" pulldown menu to build the app. Selecting "Target" tab, I specified target file name, and support/destination file directories. At "source file" tab, only the top level VI name was present.

Proceeded with "build", the app was built, when I run it, it run shortly and then program closed suddenly.

I am sure I am missing some files. I thought that build app itself will take care of all needed files and incorporate all in the final app executable.

 

1)         What am I not doing? What else I should add in the source file or other tabs that are available.

2)         Where should I place the RTE 7.1(in any specific directory relative to the app)?

3)         What else I should do in installer setting or vi setting?

4)         If I use installer, what else is needed?

5)         How about instrument or DAQ drivers? Are they automatically incorporated in the app or I should place it using source file tab functions?

 

It’s my first time building app, if there is any step by step document it will be nice to follow.

 

Your comments and support is greatly appreciated (I need to finish the work ASAP).

 

Regards,

LVLV 
0 Kudos
Message 1 of 6
(3,160 Views)
1. On the Source Files tab of Buils App, its only necessary to add such files as an ini file (if your app has one), and anything like a text file that your app might refer to.
2. Click Installer Settings tab, then the Advanced button. This is where you select the Run Time Engine and Add-ins.
3. The VI Settings tab shows you a list of all the functions, vi's and drivers, etc that have automatically been included by LabVIEW.
 
Try these and see what difference it makes.
0 Kudos
Message 2 of 6
(3,153 Views)
Maybe you open the front panel of a VI without a panel?

Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
0 Kudos
Message 3 of 6
(3,137 Views)

Thanks for your info.

From your explanation is seems like LabVIEW will include automatically all DLLs, LLBs, drivers, and necessary VIs to run the executable.

It will not incorporate any text or excel files that is used as path list or ini (we can add them using "Add Support File..."  selection under "Source  Files" tab in Build App )

In item# 2 of your response, what do you mean by "Add-ins"?

Thanks again for your help.

Regards,

LVLV

 

0 Kudos
Message 4 of 6
(3,122 Views)
No, it does not do all of that automatically. It will include the subVIs that your main calls statically. It will not include any that you dynamically call. The exe does not include any dlls that you might call. If you create an installer, any dll you call will be included but if the dll requires other dlls, it won't include them. With the installer for 7.x, you do not have the option (as you do in 8.x) to include any drivers such as NI-DAQ, DAQmx, NI-488. From the app builder window, click the Installer Settings tab. On the tab, check the Create installer box and then click the Advanced button. There, you will see all of the options that you can include.
0 Kudos
Message 5 of 6
(3,118 Views)
Dennis has covered the subject fully, so I won't add anything.
0 Kudos
Message 6 of 6
(3,103 Views)