Building model for Linux RT target from VI

[beavercreek]

Hello All,

I feel like I'm missing something easy.  Having trouble building a vi for running in a LINUX RT target.  MAYBE I MUST install LabVIEW x64 to build vi's for x64 Linux target?

LabVIEW2020:

VeriStand 2020R5:

Windows10

[Darin_G]

You should be fine with LabVIEW 32-bit. Do you have LabVIEW Real-time installed also?

[beavercreek]

Indeed, I can successfully build for PHarLap targets as well.  RT Chassis is currently still PharLap, hoping to move to Linux shortly.

[Brian.D]

There are a few other software packages I would recommend checking that you have installed that are outlined in this KB: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000001Dd2LSAS&l=en-US. Since you can compile for Phar Lap, my first guesses would be the C/C++ dev tools for Linux. Outside of those installations, I would also recommend ensuring you have LabVIEW RT and Application Builder licensed.

[beavercreek]

This was one of my confusion points... no 2020 version listed, roll with 2017?

[Brian.D]

Correct. We include that as an optional dependency with the VeriStand suite. Once you have that installed, you should not need to interact with the Eclipse environment directly, as the LabVIEW Model Generation will handle the compilation behind the scenes.

[beavercreek]

Well...

I installed and followed along far enough to successfully build the Hello world C project.  Went back into LabVIEW and have the same failure message.  I note when I open one of the created VI's, its broken.  Perhaps that is a normal condition?

I would guess that VeriStand is looking at some of the eclipse registry keys to figure out where GCC is located in the file system?

PATH=

C:\Program Files (x86)\Common Files\Oracle\Java\javapath

C:\Program Files\National Instruments\Shared\OpenVINO\
C:\WINDOWS\system32
C:\WINDOWS
C:\WINDOWS\System32\Wbem
C:\WINDOWS\System32\WindowsPowerShell\v1.0\
C:\WINDOWS\System32\OpenSSH\
C:\Program Files\TortoiseSVN\bin
C:\Program Files (x86)\imc\Shared
C:\Program Files (x86)\imc\shared
C:\Program Files (x86)\IVI Foundation\VISA\WinNT\Bin\
C:\Program Files\IVI Foundation\VISA\Win64\Bin\
C:\Program Files (x86)\IVI Foundation\VISA\WinNT\Bin
C:\Program Files\IronPython 2.7\
C:\Program Files\dotnet\
C:\Program Files\Microsoft SQL Server\130\Tools\Binn\
C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL
C:\Program Files\Intel\Intel(R) Management Engine Components\DAL
C:\Program Files\WindowsPowerShell\Scripts\HP.ClientScriptLibrary
C:\Program Files (x86)\National Instruments\Shared\LabVIEW CLI
C:\Program Files (x86)\IVI Foundation\IVI\bin
C:\Program Files\IVI Foundation\IVI\bin
C:\build\17.0\arm\sysroots\i686-nilrtsdk-mingw32\usr\libexec\arm-nilrt-linux-gnueabi\gcc\arm-nilrt-linux-gnueabi\4.9.2
C:\build\17.0\x64\sysroots\i686-nilrtsdk-mingw32\usr\libexec\x86_64-nilrt-linux\gcc\x86_64-nilrt-linux\4.9.2

[beavercreek]

I've not been able to build on three different machines.   Maybe someone could create a VI to check the file system for expected components?  or also check the registry for expected keys/paths?

[Brian.D]

Does clicking on the Linux x64 target (warning icon) provide any additional information? If you have LabVIEW Real-Time module installed and activated, perhaps the CompactRIO driver is what is causing the issue.

[beavercreek]

Ack... Success!  I installed ni-labview-2020-rt-module-x86_20.0_online_repack3  (even though it was already reported as installed) and off it went.  Will try same fix on build system #2