LV 8.5 masscompile & Tortoise SVN controlled projects

[Tomi Maila]

When masscompiling a folder that is under external Tortoise SVN source code control, LabVIEW incorrectly masscompiles also subversion internal files by interpreting them as LabVIEW files.

Tortoise SVN creates .svn folders to under each source code controlled folder. The .svn folder contains only Tortoise SVN internal files. Under .svn folder Tortoise SVN also stores unchanged versions of the files in the source code controlled folder. These files are stored in format Filename.ext.svn-base. For example Main.vi would be stored under .svn folder with name Main.vi.svn-base.

LabVIEW masscompile tries to masscompile these files even when the file extension .svn-base clearly indicates that these are NOT LabVIEW files. Thes meshes up with Tortoise SVN bookeeping and as a result masscompile cannot be used for a project that is under source code control.

STEPS TO REPRODUCE

- Install Tortoise SVN from http://tortoisesvn.tigris.org/

- Reboot

- Create a local source code control repository by right-clicking on an empty repository folder (C:\repository) and selecting Tortoise SVN -> Create repository here from the context menu

- Import any LabVIEW project to the newly created local repository by right-clicking on the project folder and selecting Tortoise SVN -> Import

- Check out the imported project from the local subversion repository to a new empty project folder by right clicking on empty project folder in Windows explorer and selecting SVN Checkout from context menu

- Tortoise SVN creates hidden .svn files in each sub folder of the newly created project folder

- Use LabVIEW to masscompile the above new project folder

- LabVIEW masscompiles SVN internal files

[James N]

Here's the steps I've done to get around this:

1. Right click on the top-level directory of your working copy (directories on your hard drive under source code control) and select TortoiseSNV>Export.

This will copy all files (minus the .svn directories) to another location.

2. Run the LV mass compile on this new directory of files.

3. Once the mass compile is complete, copy the top-level directory over top of the working copy directory.

This works in Windows since only modified or new files are copied. Any existing files in the directory (in this case the .svn directories) are left unchanged.

4. Commit your working copy to the repository.

-James

[gmart]

In LabVIEW 8.5, there is a Mass Compile option on projects themselves. This will only mass compile the VIs referenced from the project. This limits the possibilities of introducing cross link problems and would avoid the Subversion files.

[Tomi Maila]

QUOTE(gmart @ Aug 10 2007, 04:48 PM)

In LabVIEW 8.5, there is a Mass Compile option on projects themselves. This will only mass compile the VIs referenced from the project. This limits the possibilities of introducing cross link problems and would avoid the Subversion files.

Does this have the same effect as Ctrl + Shift + Run when all files of the project are in memory?

[gmart]

QUOTE(Tomi Maila @ Aug 10 2007, 09:06 AM)

Does this have the same effect as Ctrl + Shift + Run when all files of the project are in memory?

Ctrl+Shift+Run will force everything to save. The project mass compile will only save things that need to save.