Simultaneous C++ development on Linux and Windows

Question

We have a handful of developers working on a non-commercial (read: just for fun) cross-platform C++ project. We've already identified all the cross-platform libraries we'll need. However, some of our developers prefer to use Microsoft Visual C++ 2008, others prefer to code in Emacs on GNU/Linux. We're wondering if it is possible for all of us to work more or less simultaneously out of both environments, from the same code repository. Ultimately we want the project to compile cleanly on both platforms from the start.

Any of our developers are happily willing to switch over to the other environment if this is not possible. We all use both Linux and Windows on a regular basis and enjoy both, so this isn't a question of trying to educate one set devs about the virtues of the other platform. This is about each of us being able to develop in the environment we enjoy most yet still collaborate on a fun project.

Any suggestions or experiences to share?

Answer 1

Use CMake to manage your build files.

This will let you setup a single repository, with one set of text files in it. Each dev can then run the appropriate cmake scripts to build the correct build environment for their system (Visual Studio 2008/2005/GNU C++ build scripts/etc).

There are many advantages here:

• Each dev can use their own build environment
• Dependencies can be handled very cleanly, including platform specific deps.
• Builds can be out of source, which helps prevent accidentally committing inappropriate files
• Easy migration to new dev. environments (ie: when VS 2010 is released, some devs can migrate there just by rebuilding their build folder)

Answer 2

I've done it and seen it done without too many problems.

You'll want to try an isolate the code that is different for the different platforms. Also, you'll want to think about your directory structure. Something like

• project/src <- .cc and .h files
• project/src/linux|win <- code that is specific to one platform or the other
• project/linux <- make files and other project related stuff
• project/win <- .sln and .csproj files

Basically you just want to be really clear what is specific to each system and what is common.

Also, unit tests are going to be really important since there may be minor difference and you want to make it easy for the windows guys to run some tests to make sure the linux code works as expected and the other way around.