Packed library with non vi files

[TomerV]

Hi,

I'd like to use a PPL containing non vi files in a  application.

As configured and expected, the build folder for the PPL is the following :

- Build\myPPL.lvlibp

- Build\Resources\anyFile.nonvi 

If I include the lvlibp in my application project on the same computer there are no problem.

Now If I copy/paste both the PPL and the application projects on a other computer and open up the application project, I've got a warning indicating that the non vi file from the lvlibp is missing (the path shows the absolute path from the first computer). 

Is there any workround for marking non vi files relative to the output PPL in the fist place?

Regards,

Tomer.

[crossrulz]

In the build specification for the PPL, you can specify the "Support Directory".  Any non-LabVIEW files should end up in there.

[TomerV]

Sure, in my example the support directory was called "Resources"

I'm trying to get rid of the absolute file path saving method going along with non labview files in PPL.

For now, my solution is to rebuild the PPL on the second computer so the absolute file path becomes valid. Any better option?

[matt.baker]

Did you ever find a better solution for this?