Import LabWindows/CVI .uir file into LabView?

[DesertBroncoFan]

I am in the process of porting a program from Windows to RHEL 6.10 and am using the LabWindows/CVI 2013 RTE for Linux to compile and link into my RHEL 6.10 program.

We are going to be moving to RHEL 7.x in the near future and are expecting that the RTE will not work anymore.  If someone has experience with using the 2013 RTE on RHEL 7.x, what was your experience?

Assuming this doesn't work I am wondering if there is some way to "import" the LabWindows/CVI files into LabVIew, which we can get Linux support for or even if it makes any sense.

[RobertoBozzolo]

As far as I know there is no way to directly import UIR or source files to LabVIEW. One possible solution could be to create a .DLL out of your CVI application and call it in a LV project, but this will always rely on the RTE to handle events so this will not solve your problem.

I'm not experienced with Linux, but are you sure the existing RTE will not work on your new release of the OS?

[DesertBroncoFan]

---

@RobertoBozzolo wrote:

As far as I know there is no way to directly import UIR or source files to LabVIEW. One possible solution could be to create a .DLL out of your CVI application and call it in a LV project, but this will always rely on the RTE to handle events so this will not solve your problem.

I'm not experienced with Linux, but are you sure the existing RTE will not work on your new release of the OS?

---

Since I'm porting our current software from Windows to Linux, it's not really an option make the CVI application into a DLL since that's a Windows only thing.

As far as whether the current Linux RTE will run on the new version of the OS, I'm not sure.  The CVI website says that it's support to RHEL 6 but doesn't say anything about RHEL 7, so I was hoping someone here has tried it and can tell me whether it works fully or not.

[gdargaud]

The Linux CVI RTE and cvicc both work fine on Centos 7. They work on any rtm-based linux and probably on Debian too with some tweaking (but I've never tried).

I use Linux on all my production CVI systems: it's easy to lock down security (no viruses!) and discourages operators from messing around.

[DesertBroncoFan]

Thanks for the reply but we have already made the decision to convert the LabWindows/CVI GUIs to Qt.

Qt provides a much smaller footprint as far as source code when compared to CVI (or at least compared to the CVI GUIs that who ever developed the GUIs 20 years ago) and it is currently supported.