Best Practice for sharing lvlib across multiple projects?

[DDuff]

Hi All, 

What is the best practice for setting up a user developed library to be used for multiple projects? I am currently working on a project where I a have developed some VI's with associated .ctl files. I would like to be able to reuse the library with other projects, but I could not find a clear explanation on the best way to do that. Most of the documentation I have read seems to warn against just copying the corresponding system folder into the new project. 

Thanks for the help!

[billko]

I'd probably make a distribution.

[Jacobson-ni]

Most of the actual development I do is just by myself so just creating a simple VI package that will throw the library into vi.lib works well enough for me. Different projects will all just point to the same lvlib in vi.lib and VIPM handles the installation, upgrading, and versioning with minimal work needed on my end. The downside is that all projects need to use the same version of that lvlib and the project itself doesn't really track the dependencies (as in if you move to a new computer it will tell you what VIs are missing but not what package is missing) but for what I work on those aren't huge issues. It's also looking like JKI's new upcoming project dragon will address those downsides.

I know some people like to use Git Submodules. Overall this seems like a pretty clean solution once things are all set up.