On Mon, Aug 17, 2009 at 10:56 PM, Johannes Schindelin<Johannes.Schindelin@xxxxxx> wrote: > 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! Sorry, but I make a living developing cross-platform software and porting stuff among any funny combination of Linux, Windows, gcc, mingw, Intel C++ and Visual C++ you can think of. CMake makes my life easier (possible!). Given that the patches we are talking about happen to add support for Visual C++, I'd say it stepped in at the right moment. >> 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++. How do you know? Also, please note I'm not talking about *adding* a CMake build system, I'm talking about *replacing* the existing autotools build system with a CMake build system, even if they coexist for some time. What would be the point of having two build-systems, one (autotools) useless for Visual C++, the other one (CMake) apt for every platform ? -- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer) -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html