12-08-2016 10:28 AM
Hi All,
I have an application that uses PPL (Packed project library). During the build process of my application LabVIEW copies the PPL to build/My App Folder/data. I can run the application afterwards. If the PPL is deleted or moved later from this ../data/ directory I no longer can run the app.
Is there a way to dynamically link and load PPL from another location? I've tried using viSearchPath but unfortunately it doesn't work.
Thanks,
Nikita.
12-14-2016 05:06 AM
12-15-2016 01:45 AM - edited 12-15-2016 01:46 AM
Hi Sam_Sharp,
The idea was to have a set of user applications, and each app refers to only one set of (static) PPLs. I was wondering if I can get the same behavior with PPLs as with DLLs and if I can store all Shared PPLs in one place.
By default each application build process copies all static PPLs to app/data folder. So you have many copies of the same PPLs spread across application folders.
There is a workaround though. You can configure all your build specifications in such a way that they build the app files to:
builds/My Program 1/..
builds/My Program 2/..
and during the build process each build job puts and links all dependent PPLs to
builds/Shared/
Now you have only one set of PPLs stored in Shared folder to where all your applications statically refer.
12-15-2016 03:16 AM
You can make a Hard link (mklink -d) of the Data folder and have it placed somewhere else, though it'll probably introduce some other issues.
/Y
12-16-2016 01:22 AM
Hi Yamaeda,
Yes, I came to the same solution at the end. Just one correction to your message :
mklink -d creates a directory symbolic link, not the hardlink.
Nikita.