GOOF source control - Tuan?

Falagard

25-05-2006 18:21:15

Hey tuan kuranes,

I'd like your opinion on how to set up source control for GOOF.

There are many dependencies - OIS, Libnoise, Boost, Ogre, Ogre Dependencies, PLM2, OpenAL, and perhaps in the future a physics engine.

People have plenty of problems just getting PLM2 and Ogre working together, as you can tell because most of the posts on these forums are just "Help!" posts getting it set up.

I wanted to set up my own SVN server with all the deps so that people could just synch to the SVN repo and have everything they need. Obviously, I forgot that some users use VC 7.1 and others use 8.0, so I'll need to include full source for those libraries that I provided binary libs for, such as Libnoise, Boost and OpenAL so that others can compile if they need to.

The problem is that in this setup I have to manually apply PLM2 changes from ogreaddons into my SVN repo in order to get latest changes and same with Ogre.

Another problem is that wolfmanx hasn't given the greenlight for public access to the SVN, so I'm going to pull it off his server soon and have to find somewhere else to put it.

I'd like to know if you'll be using GOOF for testing functionality in PLM2 and your other projects. For example, I think the GOOF Engine and GOOF Editor is a good place to make sure CHC occlusion culling is working, impostors, painting and deforming terrain, etc.

A good place to put GOOF would be in Ogre's CVS addons, however I wouldn't be able to put the dependencies in there, and there would be a lot of additional downloading compiling and setup for users to actually get GOOF working.

So... can I have your opinion on the matter?

Falagard

25-05-2006 20:17:12

I could potentially put it in ogreaddons plus a place to download binaries for all the dependencies for both 7.1 and 8.0 (my website) and instructions on where to get the source for the dependencies and how to compile them if you want to download and compile them yourself instead.

I'd want to create a new addon in ogreaddons instead of putting it under plm2 addon though.

I'm leaning towards this way now.

tuan kuranes

26-05-2006 09:19:49

Seems the right way.
Ask sinbad for an ogreaddons folder, commit source over there and make binaries()() release on your site.
Having each dependencies in the repository would just save people the download of dependencies, not the compiling (all build system)