Transfering executable to LINUX

[sdp54321]

Hello,

I have developed a Built-in-Self-Test application for our company product. Using the Application Builder, I have an executable that runs on our machine in the Windows environment. The Government has serious issues with anything running Windows. So as an alternative, we have redeveloped our product to run on the Linux platform... more specifically Unbutu.

Does anyone know if there is any way to take this Windows based program and transfer/translate/rehost it in the Linux environment? The program in it's current form has many many man-hours in development... redeveloping the program in Linux from scratch is something we do not look forward to

Thanks,

Peter

[altenbach]

Well, you could run it on a virtual windows machine hosted on linux. 😉

You can also use the LabVIEW source, and built a new executable on LabVIEW for linux, I guess. Depending on what the program does, what drivers or system services it uses, you might need to tweak a few  (or even many) things to get it running correctly.

Running a windows application natively on linux is not possible.

[sdp54321]

So you're saying  we would need to buy LabVIEW and Application Builder for Linux @ $4500, use my existing code and hopefully not have to do too much rework to make it work. You can import LabVIEW programs from one platform to another? I assume there is a Run-Time engine for Linux... I didn't look that up.

[rolfk · Accepted solution]

---

@sdp54321 wrote:

@SO you're saying  we would need to buy LabVIEW and Application Builder for Linux @ $4500, use my existing code and hopefully not have to do too much rework to make it work. You can import LabVIEW programs from one platform to another? I assume there is a Run-Time engine for Linux... I didn't look that up.

---

Yes, yes, and yes.

As to rework it depends how you programmed your application. There are obvious things like use of ActiveX or .Net which will simply be unavailable under Linux. So if you use that in your Windows application you first have to find out if there is even a possibility to use that hardware or library on Linux in a different way than as ActiveX or .Net component and how much work it will be to adapt your app to use the Linux version.

If you use LabVIEW paths throughout and avoided to use strings anywhere where you needed a path, you should have solved that problem too.

Use of DAQmx is going to be a problematic case. There is a DAQmx for Linux which supports a limited set of DAQmx hardware. There is a DAQmx Base driver which supports a different set of DAQmx hardware and has a slightly different API with some functionality not supported.

Other LabVIEW Toolkits are most likely going to pose problems. 

On the positive side, NI-VISA, NI-488 and the native TCP/IP and UDP should simply work although you may have to get yourself acquinted with network setup under Linux.

[sdp54321]

Thanks...

The entire program communicates through RS232 so that shouldn't be a problem. I guess my only "real" problem is writing to the front touchscreen. The current touchscreen has a serial command controller with embedded graphics that I developed... The Linux system touchscreen is a completely different beast.