I understand your question now... What I've done in the past to limit access to development packages on test systems is to change the privaledges on the executable so that only certain users can run the package... This works to an extent, as long as you can trust the 'allowed' users to follow the procedures... but it does deter the caual fiddler... Of course this only works to some extent unless you change the privivedges to all the source code too, as c code is mainly just text files anyway... so it does get a bit messy and time consuming.
If you have a bit of spare budget, you could always go for one of the source control packages such as clearcase or source safe... I beleive cvi can integrate with both of these (tried it with source safe, and seen i
t done with clear case) and they will enforce the proper procedure by making users check in and out code before changing it, and handling the versioning of the changes... don't know how much these apps cost, I got source safe as part of visual studio...
Hope this helps...
John