What about using cmake for project control?

[jiandingzhe]

Currently, the source code in SVN has separate build controllers for MSVC, make for 32 bit linux, make for 64 bit linux, and mac.

So, why not using cmake as build controller generator? It has many advantages:
- It can generate makefiles, MSVC projects, Codeblock projects, Eclipse projects, and many...
- It can configure the project in a tidy manner. For example, one can trigger an option to configure whether it builds a single-float or double-float version (OGRE and Bullets has this).
- It is widely used by many people, like Ogre, OSG, Bullets, KDE. Thus it's robust and well-supported.

I'm using cmake for my C/C++ programs, and I felt it pretty good.

[Julio Jerez]

I never used cmake, but if you wan to donate a project I put it in SVN.

[jiandingzhe]

I never used cmake, but if you wan to donate a project I put it in SVN.

I'm going to write a cmake project file.
By the way, what kind of project do you use?

[Julio Jerez]

what do you mean what kind of project?
there is a visual studio, and a xcode, and a make file.

was cMake a wirite one make file once and then generate project for any system?

[jiandingzhe]

what do you mean what kind of project?
there is a visual studio, and a xcode, and a make file.

was cMake a wirite one make file once and then generate project for any system?

I mean build system.
Do you manually maintain the MSVC file, the xcode file, and the makefile?
CMake is that you write one CMakeLists.txt (or one for each directory), and it generate project for any system.

[Julio Jerez]

I manipulate the manually yes. In Mac I use xcode, and in window visual studio, a make in linux.

the is the problem I have with the automatic tools, the take away all of the simplicity of working with and IDE
However that should no be a big problem, because the project doe no change much.
so I can see me using Visual studio and editing the cMake file each time I make a change for the other platform.

I make come very useful specially when moving from one version of visual studio to the next,
for example Visual studio 2010 has so many changes that is in no backward compatible with VS2009
plus there are many Bug in the VS2010 IDE.

CMake will create the projects rather that convert them.

[thedmd]

CMake solve problem of multiple places where source code files are listed. As a bonus you will get vague MSVC and Xcode projects. For example you will not be able to decide where to put intermediate files.

CMake is PITA in our engine. So I cannot recommend you this software.

[Firefly]

I'd actually recommend Premake. It's so much nicer and easier to create a build script with and it supports a lot of platforms. It's based on LUA so you can create pretty advanced scripts if you need to.

http://industriousone.com/premake