Hi, On Mon, 17 Aug 2009, Pau Garcia i Quiles wrote: > On Mon, Aug 17, 2009 at 10:56 PM, Johannes > Schindelin<Johannes.Schindelin@xxxxxx> wrote: > > > 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. You are mistaken. We do not require using the autotools. I _never_ call "./configure" yet the Makefile magically works. Cool, huh? But here's a clue: you will probably _never_ succeed in getting a replacement of the make-based build in git.git by the maintainer. Make is just too ubiquitous and well-established for that. Having said that, a CMake-based system _in addition_ to what is tried-and-tested to be able to support all those different kinds of Microsoft Visual Studio (took me 3 attempts to write that without a Freudian) would be welcome, _if_ you succeed in making it compile out of the box on msysGit. By out-of-the-box I mean: you send a patch that adds /src/cmake/release.sh, I apply the patch (after briefly scanning that it does not install a backdoor on a machine that is not even mine, and therefore will never see even a single of my passwords typed in), run it, it compiles installs and commits cmake and cmake works. If that's not possible, I refuse to add another problem rather than solving one. If you succeed, I will ask you to do the same for Python, as you clearly proved by that point that you are a magician. Ciao, Dscho -- 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