The fact that unlike Windows Linux is multi-user may help.
I'd suggest the following. Dedicate at least one computer to run Linux. On
this computer make accounts for every Windows user that needs to develop for
Linux. Run Samba server on the computer and export either home directories or
some subdirs in home directories through Samba. Let Windows users edit sources
from within Windows on Samba shares of the Linux machine and then run native
Linux compiler remotely (through telnet/rsh/ssh). Please be warned that you
may have troubles with CR/LF and LF conventions for end-of-line in DOS and
UNIX. Try to configure Samba so that the same files on Samba share were seen
from Windows as DOS text and from Linux as Unix text, -- I recall it's
Besides, this will make transition to native Linux tools more easy in the
future. For example, you can arrange Windows users to run X servers on their
computers and run XEmacs from Linux machine to do all the work. This way they
have their MSWord/Excell handy and simultaneously can do real work in more
user-friendly environment ;-) This is not actually a joke -- most Windows
programming tools are not designed to be useful for anything but Windows
programming, I'm afraid. This way Windows is used just to draw nice pictures,
i.e., the only thing that it does relatively well.
Also, I'd suggest to switch from PVCS to CVS. Put CVS repository on Linux
machine and access it both from Windows and Linux machines. Arrange to backup
CVS repository from the Linux machine. I've used PVCS before and IMHO CVS is
much better from programmer point of view though it requires some paradigm
shift for those who is used to PVCS in the sense that CVS makes things that
were difficult with PVCS surprisingly easy :-) BTW, there are GUIs for
Windows to work with CVS.
Anyway, try it yourself before adopting something as solution.
Hope it helps.
> the cvs like tool we use is called pvcs if this helps.
> would it be possible to start the compilation by using samba
> or the likes?
> I do have some knowledge on how to do it the other way round
> (cvs on a linux machine and checking out to a windows machine
> using ssh and wincvs) The thing is, that the windows system is backed up
> regularly and hosts all our source code.
> We do indeed intend to do editing on Win32 as I am the only
> one in the company with knowledge of linux (it was hard enough
> convincing the management of using linux in the first place) and
> there are some programmers which are naturally very attached to
> their Win32 editing tools.