Create Another Version of the LabVIEW Run-Time Engine That Contains All Dependencies (vi.lib, etc).

[RyanWright]

Create two versions of the LabVIEW Run-Time Engine - 1 with dependencies (vi.lib, etc.) and 1 without dependencies.  If a LabVIEW Run-Time Engine with dependencies were to be created, it would allow you to bypass the TestStand Deployment Utility when deploying test software created using TestStand.  It would also simplify Application Builder because any native dependencies (code shipping with LabVIEW) wouldn't have to be packaged with a LabVIEW executable (only the user-created dependencies).

If maintaining two versions of the LabVIEW Run-Time Engine isn't acceptable, it would be nice to just include the dependencies in the LabVIEW Run-Time Engine.  Disk space and broadband Internet connections have almost virtually eliminated the necessity for a LabVIEW Run-Time Engine with a small disk or installer footprint, particulalry when NI hardwire driver installers take up 100s or even 1000s of MB on disk.

[ToeCutter]

Why not use LabVIEW to build an installer with the RTE and all dependencies selected but no code. Wouldn't that give you what you want?

[fabric]

---

@RyanWright wrote:

Disk space and broadband Internet connections have almost virtually eliminated the necessity for a LabVIEW Run-Time Engine with a small disk or installer footprint, particulalry when NI hardwire driver installers take up 100s or even 1000s of MB on disk.

---

Er, that's a pretty big call...

Personally, I'm quite far on the other side of the fence: The installer footprint of LV (+ drivers, etc) is probably the single worst thing about it.

[kegghead]

Agreed with Fabric. It is really hard to justify the size of a complete installer for an application that uses any form of DAQ. If anything I'd like a minimal RTE and be able to segment DAQ drivers to be statically linked/packaged with my application and only include what I need, which is pretty much the opposite of this idea.

[ErnieH]

I created a project just for the run time engine. I created several different builds. A basic one,  one with more drivers, and  one with most everything. These are all I install anymore. I also included some older run time engines. I can install this and run LV 2009 exe's and 2011 exe's in most cases.

[RyanWright]

I wasn't referring to other dependencies such as hardware drivers and driver VIs.  I was speaking strictly of the code that ships with LabVIEW.

Thanks for the ideas and suggestions everyone.

[Darren]

Any idea that has received less than 2 kudos within 2 years after posting will be automatically declined.