![](https://cdn.userecho.com/characters/84.png?1)
Allow libraries as build source (instead of folders)
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.
Antwort
![](/s/cache/37/53/3753c7f09a75995cb8afdcd9167411f1.png)
![](/s/cache/37/53/3753c7f09a75995cb8afdcd9167411f1.png)
![](https://cdn.userecho.com/characters/84.png?1)
Hi Michael,
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.
Ton
![](/s/cache/ac/59/ac594ebbe3e3845a68590c78924d00e3.png)
![](/s/cache/37/53/3753c7f09a75995cb8afdcd9167411f1.png)
![](/s/cache/ac/59/ac594ebbe3e3845a68590c78924d00e3.png)
![](/s/cache/42/40/424019a4287f654467adc1b4e5eeaf2e.png)
...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.
![](/s/cache/37/53/3753c7f09a75995cb8afdcd9167411f1.png)
Customer support service by UserEcho