SCC Question: Possible to Restrict Compilation of Code That Is Not Checked In?

[DanRichards]

Hello,

I would like to have LabVIEW (or some plug-in) prevent me and my teammates from compiling code that is not checked in. This will ensure that we always have the source code for that build checked in.

Thoughts?

Thanks,

Dan

[dstrandb]

Hi Dan,

I'd suggest taking a look at this article concerning using source control in LabVIEW. That will have links to many other articles inside of it that will help you get started. TortoiseSVN works quite well with LabVIEW for SCC. I hope this helps!

[BuddyHaun]

Just a couple suggestions. In LabVIEW 2012 you have the option to 'separate compiled code in new files' which can be very handy when working with SCC as it help cut down on checking in code that has been recompiled because of a compiler optimization. This is under the 'environment' category under options. The second suggestion that I have is to make sure that all developers are working with identical directory structures for each project down to the drive letter so that path changes between developers do not initiate recompilation to update path information. Since LabVIEW automatically recompiles I am not sure you can do exactly what you want but you can achieve the same results by only checking in valid changes to the source code.