LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

32-Bit LabVIEW RT 2019 finds a 64-Bit .so on NI Linux RT, but doesn't find the 32-Bit .so

I have a .so library, both a 64/32 bit version.  These are located at /usr/lib on a PXI running 64-bit NI Linux RT.

 

When calling a function from this library, the deployment fails, if the call library function node is configured to use the 32-bit library, with error that it was unable to find the library.  It does not fail with the 64-bit version.

 

This does not make sense to me since LabVIEW RT is 32-bit.



I saw my father do some work on a car once as a kid and I asked him "How did you know how to do that?" He responded "I didn't, I had to figure it out."
0 Kudos
Message 1 of 3
(2,327 Views)

@blackburnite wrote:

 

This does not make sense to me since LabVIEW RT is 32-bit.


Only if your RT target uses an ARM CPU. If it is an Intel CPU it absolutely certainly is a 64 bit executable (but you don't notice it from your Windows system as LabVIEW transparently cross compiles it for the 64 bit Linux target).

Rolf Kalbermatter
My Blog
0 Kudos
Message 2 of 3
(2,288 Views)

This is what I thought was happening based on the behavior but I couldn't find any documentation going into detail on the RT engine for NI Linux as far as bitness and/or how compilation occurs from 32bit-LabVIEW.



I saw my father do some work on a car once as a kid and I asked him "How did you know how to do that?" He responded "I didn't, I had to figure it out."
0 Kudos
Message 3 of 3
(2,256 Views)