cvi project/library structure for svn

[bjasper]

We're establishing SVN on an existing Labwindows CVI project/library structure and wondering if I should re-organize the structure.  Currently we're organized with a few libraries (directories) and hundreds of project applications (directories) that use the libraries.

I'd like projects to stay assigned to their older version library unless intentionally bumped to a younger version library. The .cws and .prj files identify the assignment.  Will it be necessary to pull the libraries inside each project to allow this to work?  Can we implement SVN with the existing directory structure?

[ElectroLund · Accepted solution]

Wow this is old, but I couldn't help myself, especially since this was never answered.

If I understand your scenario, I have a similar set up here.  Lots of projects, not all of which share commonality.  But there are modules, drivers, UIR files that are sometimes common.

To handle this, I have an SVN folder called "common libraries".  Then in the individual projects, I have locally set up an "externals" that links to those libraries.  This is beneficial in two ways:

1) obviously, those share libraries get updated along with updating the entire project

2) if I make a local edit to the externals portion of the code, they will get updates along with the rest of the project too.