LabVIEW Idea Exchange
When building a PPL or exe that's dependent on another PPL, LabVIEW creates the pathing automatically. I would like to specify their new location manually as part of my build spec.
Currently here are my options:
1- Select "Exclude dependent packed libraries" with PPL and target location on the same drive:
The new PPL or exe will have a relative link between the target build location and the existing PPL. This doesn't work if you want to build your exe to a /builds directory and your PPL is in vi.lib.
2- "Exclude dependent" with PPL and target location on different drives:
This creates an absolute path to the PPL, which is basically never what you want.
3- Don't "Exclude dependent": This will let you specify a layout for your new exe or PPL manually and, as long as your upstream PPL's are configured correctly, you can specify the final layout for your new build. This lets you organize your PPL's differently for development and for release, which can be handy, but it duplicates the dependencies.
I'd like a 4th option- "Act like you're going to include dependent PPL's, and let me organize new folders for them, but don't actually copy them over." I can somewhat do this right now, but it copies the dependent PPL's into my /builds directory for each build I do. I then have to delete them if I do another build that references them. If I don't delete them, LabVIEW complains that the dependency already exists at the target location.
I could accomplish this with a custom post build VI but it would have to be manually configured for each build. If I could just check a box for "Don't actually copy this here, but link it like you did copy it here" then I could do everything within the build spec.
