11-09-2020 12:52 PM - edited 11-09-2020 12:53 PM
Hi Everyone,
I have a project (not particularly large yet), that is using about 10 PPLs at the moment (the PPLs are mostly DQMH modules in a tree-like dependency structure). I have a launcher VI that calls a PPL, and that PPL might launch other PPLs (DQMH modules).
When I build the application, the PPLs go into the 'data' folder by the executable as expected. However, the executable is still dependant on the PPLs in my development workspace.
Can anyone think of why the PPLs are going into the data folder, but still the executable is dependant on the PPLs in my development workspace?
Cheers,
Tom
11-09-2020 09:50 PM
What I have done is put my PPLs in the build folder, so they are already there. In the executable build specification under "Additional Exclusions", I check the "Exclude dependent packed libraries". In the installer build specification, you can still include the PPLs.
11-09-2020 10:09 PM
Hi Crossrulz,
Thanks for your suggestion, I've given that a go but it hasn't changed the behaviour. The executable is still pointing towards the PPLs in my workspace instead of the PPLs in the data folder 😞
11-10-2020 05:19 AM
@McQuillan wrote:
Hi Crossrulz,
Thanks for your suggestion, I've given that a go but it hasn't changed the behaviour. The executable is still pointing towards the PPLs in my workspace instead of the PPLs in the data folder 😞
Sounds like you missed a step in there. I don't put the PPLs into "workspace". I work with the PPLs directly from the build folder, even in development.
11-10-2020 09:12 AM
Hey Crossrulz,
I got chatting with Derrick at the GLA summit and he helped me realise the PPLs were dependant on each other via an absolute path, so even though they looked relative (i.e. next to each other), that was inconsequential.
Anyway, after working on my documentation and ensuring my build specs were building to a relative path (relative to the dependant PPLs), I've been able to build the application properly.
Thank you for your comments.