checking if a LabVIEW project can be turned into stand-alone executable

[Rashid-Malik]

I'm working on adding some functionality to a project created with LabVIEW. One of the task given to me is to "

Produce an executable of this that will run as a completely stand-alone app from the existing project". The existing project requires that the client first purchases LabVIEW, installs it on its systems and then run the project. My boss wants me turn it into an executable project so that the client does not have to purchase the LabVIEW development environment.

My problem is that the project is huge (and I was not one of the original coders of the project). I do no have time to go through each and every property and method used in the 350 or so files to see which one is not allowing the project to be turned into executable version. (My one month only experience is also a hurdle. My organisation just gave us a month long training and after that handed us the projects to work on. Do you think one month experience is enough to start working on full fledged projects? I find that we should have been given much more time. What do you say?).

Is there a toolkit or somehing that can help me in this respect? Please guide me and let me out of my predicament. Thanks a lot.

[TCPlomp]

Maybe their is a test in the VI analyzer to test properties.

Ton

[MikeS81]

Hi rashid19672008,

i think it is possible for you. First of all find out which is the Main vi. Then localize which vi´s were loaded dynamically. After that you can start step by step building an executable. Have a high opinion of used pathes in the vi´s. It could be that you have to change something, because in an executable all vi´s lie side by side.

Which LV Version do you use?

Hope this helps for starting.

Mike

[Rashid-Malik]

Thanks Ton for the advice. I've just installed the VI Analyzer. I'll fiddle around it for the time being to get the hang of it. I'll let you know if it helped solve the problem. Thanks again. Take care. Have a very nice day.
Yours,
Rashid Malik

[Wiebe@CARYA]

You can simply let the client install the LV run time engine (on the CD I
think, or downloadable from ni). Then he can run the VI's just like you (but
not edit tem), without the need to build an executable.

Regards,

Wiebe.

[MikeS81]

---

Wiebe@CARYA wrote:
You can simply let the client install the LV run time engine (on the CD I
think, or downloadable from ni). Then he can run the VI's just like you (but
not edit tem), without the need to build an executable.

Regards,

Wiebe.

---

@Wiebe

i think this is not possible. What for i need an application builder than?

Mike

Message Edited by MikeS81 on 02-13-2008 06:48 AM

[gmart]

The VI Analyzer test - General>>VI Properties>>Built Application Compatibility does the following:

Checks for properties or methods that are not supported in built applications.  Run this test on any VIs you want to build into an application to ensure they will function properly.

[Rashid-Malik]

A very wise advice, Wiebe@CAR…! I totallt agree with you. My boss is in the field for he past 22 years. I wonder why he included this demand in the new improvements requirement for the project.

[Rashid-Malik]

Lots of thanks, George M!
I can't locate "Built Application Compatibility" under "VI Properties" (nor under any other menu).
I can only view ollowing six sub-menu's under VI Properties menu;
Broken VI
Driver usage
Platform portability
Removed diagram
Toolkit usage
VI lock state.

I am using LabVIEW 8.2. Maybe this feature is included in the version 8.5?

[Rashid-Malik]

Dear Wiebe@CAR…,
My senior programmer says that we do not want to hand over the source code to the client. If we use run time engine, we'll have to give them the whole code too.

Thanks for your advice and time.