Showing results for 
Search instead for 
Did you mean: 

Including DLLs in a PPL as a relative path

I have very similar issue, but with "exe" file being a part of lvlib (and lvlibp). Did you find a good solution of workaround?

0 Kudos
Message 11 of 13

matowc, unfortunately not. The only option is to remove non-LabVIEW files from the library and manually include them in the build specification. But this still doesn't solve the problem of having the non-LabVIEW files automatically included when referenced by another library or executable - you'd have to remember to manually include them in their build specs as well.

Using LV2018 32 bit

Highly recommended open source screen capture software (useful for bug reports).
0 Kudos
Message 12 of 13

matt.baket, thanks for reply. That's the way I do it, I hoped that maybe you've found something better 🙂

0 Kudos
Message 13 of 13