LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

lvlibp not readable only in Linux

It might help if you could attach the LLB files.  What happens if you try and open IP_wrapper.vi directly from the LLB, does it open correctly?

0 Kudos
Message 11 of 15
(182 Views)

LLBs found their demise for good reason.

 

Do you have an absolute need to go with the LLB over just a standard lvlib?

0 Kudos
Message 12 of 15
(175 Views)

smoot: yes, IP_wrapper opens cleanly from the LLB manager.

 

 

natasftw: I was using an lvlibp, but have a need to do a portion of my build automatically on Linux; Linux sees the lvlibp as invalid, presumably because it targeted Windows when it was built.  The llb was an attempt to abstract out that functionality without precompiling.

 

0 Kudos
Message 13 of 15
(167 Views)

Here's an example (in 2014) I tried to throw together to mimic your setup.  You just need to build the EXE and run it.

 

Am I on the right track or did I miss something?

0 Kudos
Message 14 of 15
(147 Views)

I certainly appreciate the time you took to develop that...I'll check it out.

 

I ended up getting a virtual windows server setup, and that allows me to do anything LabVIEW related in Windows, while also accessing text files that are modified in Linux by virtue of the fact that Windows and Linux both have access to the network drives.  So far it seems to be working well.

0 Kudos
Message 15 of 15
(145 Views)