LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Missing files when building an executable that uses PPLs

Solved!
Go to solution
Solution
Accepted by topic author matt.baker

Aha, it's finally 'clicked' on what you were alluding to and it's now working as expected.

I was thinking I had to manually set the destination of every PPL (which I wasn't prepared to do), but in fact you can simply do as below and the links remain intact. A picture paints a thousand words.

  1. Create an executable build configuration as normal. No need to manually add PPL dependencies to the main project.
  2. Create a new destination to be used for PPLs and set the 'Preserve disk hierarchy' checkbox.LabVIEW_nKPypx7S7r.png
  3. In the Source File Settings, check the 'Set destination for all contained items' for the dependencies and leave the default location. Set the destination for packed and shared libraries to the previously created destination Libs.LabVIEW_SVfJtGiwdE.png
  4. Build and find that everything runs as expected with no linking problems.

 



Using LV2018 32 bit

Highly recommended open source screen capture software (useful for bug reports).

https://getsharex.com/
Message 11 of 12
(617 Views)

For future readers: see this post as well: https://forums.ni.com/t5/LabVIEW/Best-Practices-for-Distributing-Code-in-Packed-Libraries-PPLs/m-p/4...

 

Sometimes it's necessary to put the PPLs in the 'always include' section of the build.



Using LV2018 32 bit

Highly recommended open source screen capture software (useful for bug reports).

https://getsharex.com/
Message 12 of 12
(472 Views)