views:

71

answers:

2

After some time mainly .net development, i need to work in c++ in a cross platform manner.

I don't want to give up visual studio, so my hope was that it is possible to use visual studio and the windows target as a testbuild, and then every once in a while through means of a vm test the code on linux or mac.

Does anyone have experience in how to best set this up?

I'm especially curious on how you make sure that things like the project file stay in sync with the make files which are probably needed on the *nix platforms.

+4  A: 

I'm especially curious on how you make sure that things like the project file stay in sync with the make files which are probably needed on the *nix platforms.

Since MS decided to remove support for makefiles from VS, you don't. You use something else that can generate VS project files and make sure you keep THAT set up correctly. Something like CMake.

Noah Roberts
We are using CMake to remove the dependency on the Visual Studio project system. Works nicely. http://www.cmake.org/
David
So when new files are added to the project i'll be doing that from cmake and then boot up visual studio?
Toad
@toad - more or less, yeah. VS hasn't been able to output makefiles since 2005 or earlier. Frankly, you're better off with something else if you want to do cross platform development. MS tends to discourage such things as much as possible and in VS they do so by making it pretty much impossible.
Noah Roberts
@noah roberts Any recommendations on a good ide?
Toad
There are tons of them: QtCreator, Code::Blocks, Eclipse (CDT plugin), Netbeans (plugin). These are in order of personal preference.
rubenvb
I'm a fan of Eclipse, mainly because of the task based development model and the various other team tools offered by mylyn and tight integration with other plugins.
Noah Roberts
@noah I have some experience with eclipse (used it for flex, for php and for python). It's full featured, but always has a sluggish feel to it.
Toad
@rubenvb qtcreator looks really snazzy. Very nice with the qt support built in
Toad
@Toad: it also has git, svn, mercurial, cvs, CMake, and debugging support :). And it is pretty snazzy, yeah.
rubenvb
+2  A: 

First of all, select a non-managed c++ project (to avoid the .net stuff).

After that, turn up the warning level (W3 should do), and be very careful what you do/write. IMHO, GCC is better at keeping you straight with the standard (-Wall -Wextra -pedantic -std=c++0x -pedantic), but you specify MSVC.

As Noah said, you'll need build system that is in itself cross-platform, like CMake (there are others, please don't forget that).

Remember to use platform/architecture/compiler independent types, like size_t, (u)intptr_t etc. instead of int, long, unsigned: these are a recipe for disaster and the Windows API throws these around way too much.

See here, but only/especially points 1, 2, 5, and 8 (and 9, but generalize that to svn, git, mercurial).

rubenvb
Great tips. I'll make sure to regularly test and build on other platforms.I'm guessing that the initial setup will take the longest (configuring libs, makefiles, etc) but eventually things get simpeler down theline right ?
Toad
Until you code a large portion of code and see that your assumption isn't correct on the other platform :). In theory, it should, if you get the build system right (with regards to the linker: .lib/.dll (.dll).a/.so andsoforth, paths, platform detection...)
rubenvb