including openG VIs in project file

[littlesphaeroid]

Is there a way to place OpenG library VIs in my own file hierarchy so that they can be more-easily distributed in my lab without having to install the OpenG libray on every machine? I'm finding that no matter how I package a set of VIs (llb or project), not everything gets copied in, and this is becoming frustrating for some of my co-workers.

[drjdpowell]

Why not install OpenG (using VIPM, which is quite easy) on every developement machine?  

[Prickly_Pear]

I believe that this happens most often because the items are listed under the dependencies in the project tree. This means that those items are not actually loaded into the project, but the project still depends on these VIs. Anything in the dependencies will not be included in .llv or .zip builds of the LabVIEW project. Notice at the bottom it says "Dependencies will not be included in the build so if there are any, will have to be acknowledged or sent seperately."

There are a couple solutions. You could send the files seperately. Also, you could move these files from dependencies to the actual project before you attempt to zip the project. I believe you should be able to just drag and drop them in the project explorer. This link might help in understanding project dependencies: https://www.ni.com/docs/en-US/bundle/labview/page/managing-dependencies-in-labview-projects.html

Jeremy P.