auto-exclude user-defined folders from build
Andy Soukup 10 years ago • updated 9 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).
Customer support service by UserEcho
"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:
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.
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.
- documentation (requirements docs, communication protocol spec docs)
- functional tests (has dependencies that we don't want the package to have)
- unit tests