Allow libraries as build source (instead of folders)
Ton Plomp 12 years ago • updated by Michael Aivaliotis (VIPM Product Manager) 9 years ago • 7
Sometimes my source for folder has old (or not yet finalized) VIs that I don't want to distribute, in my project I remove these VIs from the library/class, but since VIPM picks a whole folder as the build-source these VIs show up in the package.
By selecting library or class as the build source these functions wouldn't be included.
So can we agree that instead of an LVLIB it would be preferable to use an LVPROJ file as the source? I'm thinking this makes more sense. You can always put an LVLIB inside of an LVPROJ, which you should be doing anyway.
Customer support service by UserEcho
That would require me for every build to tidy up something I'm not really interested in:
The source folder. By using the project (and libraries) I have a single place to manage the code I want to release.
One option would be to create a NI-source distribution that targets a folder that is used by VIPM, that would be an easier work-around than manually exclude VIs and files in VIPM.
...and I would like to see the LabVIEW project definition parsed and used as to populate the Source File Settings of a new VIP in the builder. This would save me from having to find all the VIs on disk that are not a part of the distribution and having to manually exclude them.