Trouble Running Built Applications in OS X

[Mike_S]

Hello,

I am running Labview 8.2 on OS X and I am having trouble with the LabVIEW run-time engine. The application I built runs fine on the machine it was built on, but when I copy the application over to a different computer it does not work. I'm a little unclear on how the run-time engine is supposed to work. When I double click on the .app file, the LabVIEW 8.2 spash screen appears followed by a "Select a File to Open" dialog box. I'm not sure what file I'm supposed to select, but I assumed it was the .app file. However when I selected this file it gave an error message saying that it was not a valid LabVIEW file.

I upgraded to 8.5 and got the run-time engine for 8.5 and the same thing happens.

Am I missing something? Is there any documentation for the run-time engine? Most of the stuff I've found seems to only apply to Windows.

Thank you,
Mike

[andre.buurman@carya]

Are you sure that the executable you build is build correctly?

Seems like it can't find the main VI.

Try and select a dummy VI on the run-time only machine and see if it starts.

André

Message Edited by andre.buurman@carya on 09-12-2007 08:53 AM

[Mike_S]

I'm not sure that I am building the app correctly. I made an extremely simple, one VI project and compiled that, but it also said that was an invalid LabVIEW file.

I'm a little unsure about your reply André. The compiled program is a .app, so there aren't any VIs. There are four files that are created by the build: program.app, program.aliases, a preferences file and a preferences.bak file. When I double click the program.app file, it shows the LabVIEW spashscreen, then asks me to select a file. If I select the program.app in this file select dialog, it says that it is an invalid LabVIEW file.

Thanks for your reply,
Mike

[andre.buurman@carya]

I ment instead of selecting the .app select the .vi the app was built from.

It is possible to start VI's in a run-time only environment using a build executable.

André

[Mike_S]

I'm still not having any luck. When I try to run the built executable on the machine that LabVIEW is installed on it works fine, but it does not work on the run-time only machine. This is with the extremely simple, single VI program.

What kind of settings in the build specifications could mess the executable up enough to make the run-time engine think that it's not a valid LabVIEW file?

[andre.buurman@carya]

Have you tried re-installing the run-time engine?

Or build an installer on the dev machine and use the installer to install the exe with a new runtime (don't forget to uninstall the current runtime first).

André

[Mike_S]

I haven't tried reinstalling the installer, but it was a fresh install on a computer fresh out of the box. I'll give that a shot though.

As for making an installer, I think you can only do that in Windows.

Thanks for your reply,
Mike