Hi, On Mon, 17 Aug 2009, Pau Garcia i Quiles wrote: > On Mon, Aug 17, 2009 at 9:53 PM, Johannes > Schindelin<Johannes.Schindelin@xxxxxx> wrote: > > > Of course, we could have a script that verifies that the .vcproj files > > contain reference the appropriate files (which it would know about by > > being called from the Makefile and being passed the file names), maybe > > even be able to edit the .vcproj file if it is missing some. Should > > not be too hard in Perl. > > You'll need to special-case for Visual C++ 2010, which is different > and incompatible with previous versions. Ah, my beloved Microsoft time tax! > Hence my suggestion for CMake: appropriate project files would be > generated for the tool the user chooses, be it VC++ 2005, VC++2010, gcc, > Borland C++ or anything else. The problem is that this will bitrot even more, as nobody will use it for gcc, Borland C++, XCode, Eclipse or anything else, except for Microsoft Visual C++. Ciao, Dscho