LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

how to export a labview programm

Hello community,

 

how do I export a Labviewprogramm that I wrote from one Comuter to another. I need to include some VI`s I used on computer 1 to be included in the exportet program becaus I don't have them on computer 2.

 

thanks in advance,

 

Florian

0 Kudos
Message 1 of 6
(4,087 Views)

Did you build the application in a project? If so, its as simple as selecting Save for Previous Version... from the project file menu. In the resulting dialog box, select the current version of LV (so it doesn't actually back save it) and press Save. In the last dialog box navigate to the directory where you want the copy and select Current Folder.

 

Mike...

 

PS: if the code isn't in a project, it should be. Create a project for it and then follow the above steps.


Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 2 of 6
(4,085 Views)

The "save for previous" trick does not require a project. Simply do it from the toplevel VI. (This works without problems as long as LabVIEW can figure out all dependencies. Of course if you have dynamically called VIs, you need to copy them seperately.)

 

If you have a project and a license for the application builder, you can also build a source distribution.

 

(If the missing VIs are from a driver, toolkit, or module, I would recommend to install them on the second machine from scratch)

 

0 Kudos
Message 3 of 6
(4,074 Views)

mikeporter wrote:

PS: if the code isn't in a project, it should be. Create a project for it and then follow the above steps.


Shouldn't he only create a project if he is targeting building an application or has lots of files that he needs to organize?

 

I would use "Save As" -> "Duplicate Files to New Hierarchy to New Location" and choose a new location.  You can now zip the contents of this folder which contains all the vi's and sub-vi's.

But maybe this is the old way of doing things.

 

-SS



0 Kudos
Message 4 of 6
(4,069 Views)

truckfighter,

 

Are you talking about porting a built LabVIEW application or porting a bunch of LabVIEW vi's from one computer to another?

 

Regards,

 

-SS



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

No, you should be thinking of the project file as a place to organize all the files associated with a project. Plus working in projects can help to identify and resolve conflicts - and a bunch of other neat stuff too, like renaming files.

 

Mike...


Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 6 of 6
(4,062 Views)