Labview Runtime Engine 8.6 !!INSTALL!!
Labview Runtime Engine 8.6 >> https://blltly.com/2tt41R
Labview Runtime Engine 8.6 !!INSTALL!!
Hi, I'm a new Arch user having migrated from Ubuntu a few weeks ago. I've been stuck for several days trying to get the National Instruments Labview runtime engine installed. It is an easy process on Ubuntu so it must be possible with Arch. I'd prefer not to operate outside of pacman (ie. installing with rpm or dpkg) based on what I've read in the forums.
The Labview runtime engine is a free download from National Instruments and allows programs that are generated by the Labview developer package (expensive) to be run on any box without having the licensed Labview software installed. This is handled with two .rpm files that one downloads from the NI website after registering there. You must download the .rpm files appropriate for the version of Labview that generated your executable. (Note that executables generated by Windows Labview and Linux Labview are not interchangeable) For reference, those files can be found here:
and rebuilt lvtest from scratch, but I still can't get my Labview applications to run. For clarification: these separate application files are what I was referring to as "executables" since that is how they are identified in the file manager. They are not part of the .rpm files I'm trying to install. These custom-made executables are built on another box that has Labview's full developer software package. They will run on another computer without the licensed Labview software provided the two .rpm files are installed correctly. The .rpm files generate the (free) runtime engine. So when I set this up with alien -> .deb -> dpkg on Ubuntu, a simple double-click on the application/executable file starts the Labview runtime engine and all is well.
OK, I'm making progress. I took a look at the successful runtime engine install on the Ubuntu box. I found that dpkg copied the alien-converted rpm packages to /usr/local/lib/ with root privileges. The only way I can launch an application (foo) generated by Labview's developer software (on a different computer that I don't have access to) is to double-click on the foo icon. According to the icon properties, this tells Ubuntu to "execute". I have no idea how to run it from the terminal, including just typing foo. And yes, the permissions are executable.
Ka-ching! Well solved Xyne. Your first suggestion did the trick. The Labview runtime engine is now functioning here on Arch. From the runtime GUI I can open foo and it runs perfectly. The export LD_LIBRARY_PATH stuff is also necessary before running foo.
where foo is the Labview application built previously on another machine. I was expecting that typing foo at the terminal would open the runtime engine AND foo. But it only opens the former and stops there, waiting for me to specify an application/executable. It appears to be ignoring foo even though it was explicitly installed by PKGBUILD. So I'm essentially using foo to only open the RTE -- from there I must open foo from the menu. Why is that
That's essentially what's happening. Since I can't find any script in the package of .rpm files, the only way I know how to get the runtime engine (RTE) going is by launching the pre-built application foo. This starts the RTE, but it is not aware of foo so it halts and asks me to open any file of my choice via the GUI. So I click through the directories until I get to foo. It's not the clean solution I was hoping for (i.e. what happens with the RTE on Ubuntu as described in earlier posts) but it is a solution.
For the sake of completeness, here is the detailed procedure for installing the LabVIEW runtime engine (RTE) on Arch, relying entirely on pacman. This assumes you have an application `foo' that was built by the premium version of Labview with the developer package. You must know the exact version of Labview/Linux that produced foo. Download the corresponding two .rpm files that will generate the RTE after registering on the NI website. Extract the various libraries from the .rpm