Linux VI with Runtime Engine Only

[Fox_Mccloud]

Hello Guys.

I have not read all the replies but I think noone has clarified this yet.

When "compiling" a program in labview. The builder is NOT making the code to machine code. It's just smacking all the vi:s that the program needs into a llb in some way.

You can visualise this by renaming your executable to <applicatio_name>.llb and open it with labview.

The Runtime engine does simply what the development suite does execept that you have no editing options.

Cheers.

//Beckman

[Wiebe@CARYA]

"Fox_Mccloud" <x@no.email> wrote in message news:1171372209218-477378@exchange.ni.com...
Hello Guys. I have not read all the replies but I think noone has clarified this yet.When "compiling" a program in labview. The builder is NOT making the code to machine code. It's just smacking all the vi:s that the program needs into a llb in some way.You can visualise this by renaming your executable to &lt;applicatio_name&gt;.llb and open it with labview.The Runtime engine does simply what the development suite does execept that you have no editing options.Cheers.//Beckman


This is not the compile proccess that you are describing. It's the building an application proccess.


Each VI is compiled when you run it (or recompile it). When you run it, LabVIEW runs the machine code inside the VI.


When you build an application, the VI's, with the compiled machine code inside them, are put inside an llb. That's not compiling, that has been done already.


The way the rte and development env. execute compiled VI's is exactly the same. But the rte needs compiled VI's. The development env. can recompile the wires.


Hope that clears it up.


Regards,


Wiebe.

[Wiebe@CARYA]

To summaries, and close the thread with some new LV8.2 info:
"Wiebe@CARYA" <wiNOebe.walsSPtra@carAMya.nl> wrote in message news:45cc3a7c$1@PYROS.natinst.com...
Hi,


We're trying to start a VI on a Linux system, with only the runtime engine installed. But we're having a few problems...


First, if the runtime engine installed without errors ("rpm --install labview71-rte......i386.rpm" and "rpm --install labview-rte-aal......i386.rpm") how can I know for sure that it's working? I can't find any file that indicates that it is installed...


Must have done something wrong. Still clueless about this.


Is it possible (just like under windows) to start a VI with only the runtime engine? What should I call on the shell to start a VI?



This is only possible by building an executable. Until LV7.1, you can build an executable without a vi in it. When the exe is started from the command line with a vi as parameter, the main vi in the exe is not started, the parameterized VI is. Works both under Linux and windows.


Is it possible to run a windows VI under Linux, with only the runtime engine? I read somewhere on www.ni.com that to run a VI a rte of the LabVIEW version used to build the VI is needed. But is LV7.1 for Linux the same version as LV7.1 for windows? Is the Linux runtime engine capable of running the windows VI?


No it's not. The compiled code needed to run a VI under windows and Linux differ. So the vi needs to be recompiled when the OS is switched. To recompile the VI, a development version of LV is needed.



In short, what we like to do is: Use windows to develop some VI's with serial communication. Copy the VI's to a Linux system. Start the VI's.



The basic setup:


One VMWare Linux or normal Linux desktop system (we used CentOS).
One (single board computer) SBC with Linux on it (we used CentOS, but LV should be picky about this).
Install LabVIEW Professional 8.2 on the desktop.
Install LabVIEW Runtime Engine 8.2 on the desktop.
Build a "splash screen" executable.
Put it on the SBC.
(Test it.)
Develop VI's on the desktop, and copy them to the SBC.
Start the splash screen application, with the main VI as parameter.


Note that we used CentOS for a few reasons:


It is binary compatible with RedHat.
It has support for RPM's. LV is supplied in RPM's, so for Linux beginners it's very easy.


The down side is that even the minimal install is 690 MB, without even an X server... It's OK for our application, we have a 2 GB disk. But it should be possible to remove unnecessary stuff, and reduce Linux to 20-50 MB.
Any ideas are greatly appreciated.


Wiebe.




Well, we finally got a LV8.2 Linux version (we have a software lease, and are alliance member).


Things changed a bit in LV8.2. It is no longer possible to build an executable without a VI in it. Also, the VI in the executable is started, even if the exe is started with another VI on the command line. So, to start a VI with only the runtime engine installed, one needs an exe with a "splash screen". A simple VI that hides it's own front panel works fine.


Now the fun part starts... Getting the hardware to work.


Regards,


Wiebe.