+2
Under review
Andy Soukup 4 years ago • updated 3 years ago 5

when creating a new VIP, automatically "exclude from build" folders that match user-defined strings (preferably compatible with labview regular expressions or PCRE). I suggest this because we have a well-defined file structure in our source code repository. all files in certain folders are never included in the build because they are only used during development. It would be nice if this could be auto-configured but only when creating new packages (so there are no surprises when opening an existing package).

"It would be nice if this could be auto-configured but only when creating new packages (so there are no surprises when opening an existing package)."


Can you explain this some more?

Here is one implementation scenario:

  • Have a global setting under Tools>Options: "Default exclusion filter for new packages:<insert regular expression here>. Then when you create a new package build spec, VIPM would copy the exclusions filter to the new spec and apply it.
  • Now each package build spec would have a copy of the exclusion filter. You could go in and edit this exclusion filter for the spec and change it (if you want), to be different and then re-save it.

this would give you the flexibility to override the default exclusions once they were initially applied. this isn't really a requirement, it is just nice to have the ability to override these things sometimes.


your implementation scenario pretty much nails what i'm looking for. an exclusion filter for each package would suffice.


if you go the route of a "default exclusion filter" applied to VIPM in general, that would lend to creating default settings for other things (e.g. default pre/post build scripts).  I like this option, but due to the complexity it's not a simple upgrade and therefore less likely to be implemented.

Another thought to this. If you were allowed to use a LabVIEW project file to define your build VIs, would this be a better approach? You would just not include files in the project file that you don't want to package.
i'm looking to specifically exclude the following:
  • documentation (requirements docs, communication protocol spec docs)
  • functional tests (has dependencies that we don't want the package to have)
  • unit tests
we would typically include some of these in the project to make them easier to manage so i don't think the project approach would be the best for us.