"cross-compilation" with labview

[caillotantoine]

Hello, 

I just had a call with a customer that have a problem: 

we cannot install multiple version of drivers to develop applications with different driver versions. 

This problem happens to our partners.

Example:   

I have a customer that want to uses LabVIEW 2014 and another one that uses LabVIEW 2017. So I would like to make a project with 2014's dependencies and another project with 2017's dependencies. 

So the idea is to manage the dependencies in the project itself.

Best regards, 

Antoine

[crossrulz]

The problem with drivers is that they typically cannot be installed side-by-side.  So if you change the project, you have to uninstall one version and install the desired one.  This can be very time consuming.  Use a VM (Virtual Machine).  Then you can have a VM for the 2017 installation with its drivers and another VM for 2014 and its drivers.

Now if we start talking about reuse code packages, I am in agreement that those should be somehow managed at a project level.

[caillotantoine]

Actually, that's what we are doing here in NIF. but the customer informed me that he cannot use VMs because they do not have powerful enough computers to rum comfortably VMs with LabView.

[manu.NET]

It would be nice to have a LabVIEW project ...

=> Linked to the LabVIEW source files (Already exist)

=> And linked to the Drivers needed (New)

=> And with a kind of "TestStand deployment utility" to package all files required to re-generate the project on an other computer.

So we could have a complete Source File+Drivers management ... 

The goal is to be able to rapidly clone a complete development environnement.

Manu.

[Darren]

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