[cvsnt] OT: Which VS6 files to store in CVS?

[Petr Prikryl]

Hi

[cenzored for brevity ;]
> On Thu, 27 Feb 2003 20:21:47 -0300, "Ricardo Fukasawa"
> >Well, I am not an experienced Visual C++6 user, but I have 
> been using CVS to store my Visual C++6 programs and I only
> keep there the .c, .cpp, .h, .dsw and .dsp files.
> >
> >All the rest (.ncb, .opt, .plg, .ilk, .pch, .sbr, .pdb, .idb, etc.) I
keep
> >out of CVS and Visual C rebuilds them without a problem. I 
[...]
> I was really confused by the many extra files that appeared when I
> ported the source up to Win32 level...
> I will just store these then. But what about the mak file, that was
> the one I started out with when I ported the stuff...

As Lindsay wrote (i.e. don't forget the rc files).
>
> >Can someone familiar with VS6 please advice which files apart from
the
> >*.C and *.H sourcefiles and the *.MAK file should be version
> >controlled?
>
> *.dsp - the actual project file
> *.rc - resource files

If VC++ is the major tool to use (i.e. you are not combining 
the build process with something else), then it is easier to 
use *.dsp and *.dsw files instead of makefiles. Later, you can
always export dsp into the makefile form.

If you are using bitmaps and icons, then you probably want
to store also *.bmp and *.ico. Be careful to add them as binary
files (i.e. "cvs add -kb my.ico my.bmp").

When adding icons, dialogs and other thing, the resource.h
is also automatically generated. This should also go to the 
repository, even though it was created automatically.

You can always try "cvs -n update >u.lst" to get the information
about what was added into your cvs repository.

You can always try "cvs -d myrepository export -d mytmpdir -D now
MyModule"
to get the fresh copy of what is stored inside your repository.
Then you can compile it from scratch and see if everything is O.K.

Petr
-- 
Petr Prikryl (prikrylp at skil.cz)