CVS questions

Tuan,

I'm looking at putting my MapEditor source into CVS, and I want to know how you deal this:

You have the PLM2 code in addons, and ask users to copy into ogrenew.

How do YOU have your code set up? When you are working on PLM2, do you work on the code that you've copied into ogrenew, test it, compile it, etc. and then manually copy your .h, .cpp and whatever files back into your addons folder and then do a commit?

That seems wrong, but I can't figure out how else it would be done.

Clay

Folders copied into Ogrenew still have CVS subfolder, then being "commitable" and "updatable"

Here what it gives, as I have to handle each plsm2 folder separatly :
(folder names are for exemple, you'll get the thing.)

cvs update ogrenew // <= update Ogre as usual
cvs update ogrenew/Plugin/paginglandscape2 // <= update plsm2 Plugin
cvs update ogrenew/Samples/paginglandscape2_demo // <= update plsm2 Demo
cvs update ogrenew/tools/mapsplitter // <= update plsm2 mapsplitter
cvs update ogrenew/Samples/media/paginglandscape2


Next is I have to commit 4 folders :


cvs commit ogrenew/Plugin/paginglandscape2 // <= update plsm2 Plugin
cvs commit ogrenew/Samples/paginglandscape2_demo // <= update plsm2 Demo
cvs commit ogrenew/tools/mapsplitter // <= update plsm2 mapsplitter
cvs commit ogrenew/Samples/media/paginglandscape2


You then know why all plsm2 media are in a subfolder of media instead of mixed with Ogre core media (bad.)

I only do the ' manually copy' from ogrenew to ogreaddons for files that are directly in Ogre Folders. (root makefiles, paginglandscape2.cfg, resources.cfg.) And that's a pain.

Okay, cool - that sounds good