LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

shared libraries not found using Conditional disable

we're using a conditional disable structure to check for the target type operating system. if windows, call a function in a dll. if RT, call s function by the same name in a dll with a different name. if Unix, call a function in a library with a different name.

 

when i open the vi in windows, i get a message saying that it can't find a shared library (the Unix file). i click cancel and the vi will load.

 

any way of avoiding this message? we're using LabVIEW 8.0.

0 Kudos
Message 1 of 4
(2,459 Views)

Hello,

 

Have you tried including your files within your distribution so that they can be loaded no matter which OS you are using? Then, as determined by your code, it will call the appropriate file because it will always be available.

 

-Zach

0 Kudos
Message 2 of 4
(2,436 Views)

we are targeting windows, labview RT, Linux. so i took one of my dlls (don't remember if win32 or RT) and copied/rernamed to the linux file name. it seemed to make LabVIEW happy but i thought it was a little kludgy.

0 Kudos
Message 3 of 4
(2,429 Views)

chucky wrote:

we are targeting windows, labview RT, Linux. so i took one of my dlls (don't remember if win32 or RT) and copied/rernamed to the linux file name. it seemed to make LabVIEW happy but i thought it was a little kludgy.


Interesting. You probably won't need a copy of the actual file. A simple emtpy (0 byte length) file with the appropriate name might suffice

 

I would consider this in fact a bug. The code in the disabled diagram should not even attempt to reference an external file, especially since there is no way it could ever possibly use the COFF format DLL shared library image on a Unix system. So why even check for that file to be present??

 

Rolf Kalbermatter

Rolf Kalbermatter
My Blog
0 Kudos
Message 4 of 4
(2,415 Views)