title: Cross-platform svn management (Makefiles & Visual Studio)
body: <p>I'm working on a little game called <a href="https://code.google.com/p/freegemas/" rel="nofollow noreferrer">freegemas</a>, it's an open source version of the classic Bejeweled written in C++ and using <a href="http://www.libgosu.org" rel="nofollow noreferrer">gosu</a> as the graphic API. I've been developing it under Ubuntu Linux as usual, but the other day I wanted to give it a try and I compiled it on Windows using Visual Studio 2005 (which I had never used before). The program worked flawlessly.</p>
  
  <p>To compile it on Windows I manually copied all the source and header files to a new project on MSVC, but I would like to adapt the SVN so I don't have to recreate the project every time I want to compile it.</p>
  
  <p>Therefore, the question would be: What's the best way of organizing the svn so I can have, on the one hand, a Makefile to compile the project in Linux, and, on the other side, the MSVC project's files? Right now I've got a simple folder called <code>trunk</code> with all header, source and resource files on it.</p>
  
  <p>I've never used Visual Studio before, so I don't know which files are the most important either. Maybe some of those files are auto-generated and do not need to be svn-versioned.</p>
  
  <p>Thanks in advance.</p>