Building exe or installer or something....

[dsasorin]

Hi. I have Labview 8.5 Professional on a PC.

I made a .vi which read from a device on serial port.

Write in spreadsheet file, then zip file....All works fine. I also have 4 dependinces (subvi)

So, my .vi, included subvi's are ok.

1. Now, I want to make an exe file, to run on another computer which hasn't Labview.

I saved the project, right click on "Build Specifications" / New / Application (EXE).

Build ok. (370 KB)

I went on another machine, and I run the Application.exe and I saw that I have a.vi running , not a pure exe. And of course there is no way to run the Application.exe, because there is no Labview installed.

I want to have a pure exe, not a covered.vi. At least an .exe, which works fine.

2. Then I Build an Installer. I checked the Labview run-time engine to be included.  Build ok. (64 MB)

I went again on another machine to install the kit, but surprise, i can't run the vi, Windows doesn't know to open the vi.

What's wrong ?

 If I install the kit on my machine, and run the resulted vi (at c:\Program Files\........vi), and I run the vi, Labview can't find automatically dependencies. It wants to point him the dependencies.

3. Then I build a distribution. But Labview can't find at Dependencies, in vi.lib,  PathToUNIXPathString.vi : "[Warning: has been deleted, renamed or moved on disk]"

I must say that I don't have such a file on my computer.

I don't know why it show me that error.

In conclusion:

I want somehow tu run a .vi on another machine without Labview being installed.

I don't care if the kit is big or not. I preffer to have, thought, a single exe.

It is possible ?

PS: I looked for a complet tutorial, to help me step by step, how to build an exe, or an installer, but.... no succes.

[TCPlomp]

Here is a KB article on building executables.

---

dsasorin wrote:
...

I went on another machine, and I run the Application.exe and I saw that I have a.vi running , not a pure exe. And of course there is no way to run the Application.exe, because there is no Labview installed.

I want to have a pure exe, not a covered.vi. At least an .exe, which works fine.

 The executable you use is a pure exe. I assume you didn't customize the title of the VI window.

2. Then I Build an Installer. I checked the Labview run-time engine to be included.  Build ok. (64 MB)

I went again on another machine to install the kit, but surprise, i can't run the vi, Windows doesn't know to open the vi.

What's wrong ?

 If I install the kit on my machine, and run the resulted vi (at c:\Program Files\........vi), and I run the vi, Labview can't find automatically dependencies. It wants to point him the dependencies.

You don't run a VI you run the executable installed by the installer (make sure the executable build is included in the build), the installer can create shortcut icons on the desktop or start menu (By default an icon is installed on the desktop I think)

---

 Ton

[Hueter]

Dsasorin

When you create an exe correct it should generate a exe in the directory specified on the information page of the application properties window. This exe can run on any machine with the run time engine and appropriate driver.

When you are configuring the application properties page, be sure to set your top level VI and include your subVI's as always included on the source files page.

After you configure the application go to the preview page and select generate preview.

You should see 3 files:

Application.aliases

Application.exe

Application.ini

 

Then after you build the VI check the folder indicated on that page and you should find these 3 files. If you are still having problems with this try creating a very simple VI add it to a project and create the exe. If this doesn't work we know that your VI is not causing the problem, you are either choosing an invalid option or there is a problem with your LV install. 

Hunter

Message Edited by Huter on 02-20-2009 02:11 PM