Search the Community

Hi there, I had to use packed libraries (PPL). No problems... But then I also had to deploy my code with PPL's. As already known there are several issues noted http://labviewjournal.com/2011/10/packed-project-libraries-part-2/?relatedposts_exclude=99 out there. I wondered if there is a solution to this with 2013 but as far as I know : nope. If somebody knows a good simple way please let me know. While experimenting I found a way how to do it. I attached some code and am curious if it works for others too.... The setting was like this. I had a LibC and it is used in LibA. In LibB I had to use LibA and LibC. In the Main.vi I use LibA and LibB. It's a usual use case I hope . A library LibC used by two plugin's. Since Labview includes the lvlibp's in each distribution you run into a name conflict when using and deploying the lvlibp's and the exe in the end. The solution would be to exclude them during build. But this wasn't possible. It seemed ! Naive as I am I had a look on the build specs in the project files, and found an node called "Bld_excludedDirectory" but only for source distribution. I copied this entry from there to the spec for the PPL and ..... it worked fine! This came out at last. <Property Name="Bld_excludedDirectory[0]" Type="Path">../Shelf</Property> <Property Name="Bld_excludedDirectory[0].pathType" Type="Str">relativeToCommon</Property> <Property Name="Bld_excludedDirectoryCount" Type="Int">1</Property> So when the project is load into memory the build classes keep this info and proceed with it as with source distribution. (One draw back is, that when resaving the whole project or edit the build spec in the editor it is gone again ! ) It's now in principle also possible to have a custom exclude path for the build. then I had doubts: Am I doing something illegal? I hope no..... I hope I could help someone with this Info. Best Regards Barns LibALL.zip