topic Re: Linux labview unable to run executable in LabVIEW

Linux labview unable to run executable

LauraFB — Thu, 17 Dec 2009 15:57:26 GMT

I would like to run a labview executable and have been unable to do so. The executable was built on a Windows platform using Labview 9. I'm using a Linux box and when I try to run the executable from a terminal I receive the error message "bash: cannot execute binary file" and if I try to double-click the executable on the desktop I receive the error message "Nautilus has no installed viewer capable of displaying ".

I've already installed the Linux labview runtime engine.

Am I missing files that need to be associated with the executable? Or is there an environment variable set improperly?

Thank you,

Laura

Re: Linux labview unable to run executable

Dennis_Knutson — Thu, 17 Dec 2009 17:22:22 GMT

An exe's binaries are not the same on different OS's. You cannot run any windows exe in Linux, no just a LabVIEW exe.

In order to run on Linux, you need to load the source code with the LabVIEW for Linux development environment and rebuild the exe.

Re: Linux labview unable to run executable

smercurio_fc — Thu, 17 Dec 2009 18:16:12 GMT

You could also try Wine, but that apparently has mixed results (mostly on the "not working" side).

Message Edited by smercurio_fc on 12-17-2009 12:16 PM

Re: Linux labview unable to run executable

LauraFB — Thu, 17 Dec 2009 19:07:05 GMT

Ah, I was afraid that was the case. I have Labview (8.5) on the Linux box, but I do not see where I can build an exe; how is this done? The project also seems to be missing a number of files when transfered from Windows to Linux; how do I find these missing files?

Thank you for your responses.

Re: Linux labview unable to run executable

CoastalMaineBird — Thu, 17 Dec 2009 19:13:11 GMT

As mentioned, to build a LINUX executable, you have to use the LINUX LabVIEW.

You need the FULL or PROFESSIONAL versions of LabVIEW for Linux, or you need to purchase the APP BUILDER add-on.

Those allow you to create a stand-alone executable.

"Stand-alone" means you don't need the LabVIEW environment, but you still need the (free) LabVIEW RunTime.

If you only have LabVIEW BASIC for Linux, then your code could be using some advanced VIs that aren't available in BASIC LabVIEW, and that's why they're missing.

What files are missing?

Message Edited by CoastalMaineBird on 12-17-2009 01:13 PM

Re: Linux labview unable to run executable

smercurio_fc — Thu, 17 Dec 2009 19:13:45 GMT

CoastalMaineBird wrote:
You need the FULL or PROFESSIONAL versions of LabVIEW for Linux, or you need to purchase the APP BUILDER add-on.

That is not correct. The Full version does not contain the Application Builder. The Application Builder is included in the Professional or Developer Suite version.

Re: Linux labview unable to run executable

LauraFB — Thu, 17 Dec 2009 19:21:07 GMT

I am running the full development version of Linux labview 8.5. However, I do not see any tool to build an executable.

When I copy the labview project from the windows machine to the linux box and then try to open the vi, labview is unable to find a number of files including NiRioSrv.so and nirio_resource_hc.ctl as well as a number of FPGA vi templates, controls, and xnodes.

Re: Linux labview unable to run executable

smercurio_fc — Thu, 17 Dec 2009 19:28:28 GMT

LauraFB wrote:
I am running the full development version of Linux labview 8.5. However, I do not see any tool to build an executable.

As I noted, the Full development version does not contain the Application Builder. You will need to purchase this as an add-on.

When I copy the labview project from the windows machine to the linux box and then try to open the vi, labview is unable to find a number of files including NiRioSrv.so and nirio_resource_hc.ctl as well as a number of FPGA vi templates, controls, and xnodes.

You need to install the drivers for the hardware that was being used. Of course, this assumes there are Linux drivers available.

Re: Linux labview unable to run executable

LauraFB — Thu, 17 Dec 2009 20:20:22 GMT

Hmm, it doesn't seem like it's really a 'Full' version then . . . instead of running the exectuable directly on the Linux box, we'd like to use the labview web publishing tool. We've followed through the steps in the web publishing tool gui on the Windows machine, but are unable to access the webpage from the VI. Are there ports which must be enabled or system variables which must be changed? I also tried to see the vi using the remote panel connection tool on the linux box but received an error message regarding enabling the web server?

Re: Linux labview unable to run executable

JoeFriedchicken — Thu, 14 Aug 2025 17:50:09 GMT

This is outside of my area of expertise, but 'NiRioSrv.so' and 'FPGA vi templates' tells me your application most likely uses both the LabVIEW Real-Time mobule and the LabVIEW FPGA module.

Both of these modules are not available on Linux [1] [2], which means your application will not load or run.

[1] LabVIEW Real-Time Module Release and Upgrade Notes
https://www.ni.com/docs/en-US/bundle/371375c/resource/371375c.pdf

[2] LabVIEW FPGA Module Release and Upgrade Notes
https://www.ni.com/pdf/manuals/371572e.pdf

Re: Linux labview unable to run executable

hecmar.arreola — Mon, 21 Dec 2009 21:53:22 GMT

LauraFB wrote:
Hmm, it doesn't seem like it's really a 'Full' version then . . . instead of running the exectuable directly on the Linux box, we'd like to use the labview web publishing tool. We've followed through the steps in the web publishing tool gui on the Windows machine, but are unable to access the webpage from the VI. Are there ports which must be enabled or system variables which must be changed? I also tried to see the vi using the remote panel connection tool on the linux box but received an error message regarding enabling the web server?

I'm not an expert on cross-platform compatibility problems with LabVIEW, but...

I don't think you can access a Remote Panel running on Windows from a Linux or Mac workstation. The problem is that the Remote Panel feature relies on the runtime engine, and the runtime engines would be different on different platforms.

LabVIEW Web Services, on the other hand, would be considered cross-platform (from an accessability standpoint) but I doubt that is what you are looking for.