Hi, On Wed, Aug 19, 2009 at 10:29 AM, Johannes Schindelin<Johannes.Schindelin@xxxxxx> wrote: > Hi, > > On Wed, 19 Aug 2009, Marius Storm-Olsen wrote: > >> The full IDE support is secondary, first because you *can* use the IDE >> already, and second because it'll be harder to whip something up which >> guarantees that the vcproj support stays in-sync at all times and won't >> lag behind. > > I think the point of Frank's patches is to make Visual Studio users > comfortable with Git. You cannot ask those to use a build process or an > IDE they are not used to. > I don't know Frank's intentions behind adding the .vcproj files. Maybe it was just easier for him to create them, rather than hacking the Makefile? As a Windows / Visual Studio user, I have to agree with Marius' points here. Most importantly, get the git code itself to compile with Visual Studio. Did anyone do any benchmarking yet? I wouldn't be surprised if we got some speed improvements from this. Also, it will no longer impossible to use the Visual Studio debugger. Supporting the Visual Studio compiler in the Makefile seems like an excellent and maintainable way of getting the build up and running. I can't speek for all Visual Studio users, of course, but personally I couldn't care less about the .vcproj files. I use other IDE's for developing on Windows (qt-creator, eclipse-cdt), so for me .vcproj files would be useless. The Makefile should work from any IDE. In my experience, all of qt-creator, eclipse _and_ Visual Studio support running any make-like program, and parse the compiler errors correctly without using sed or other kinds of magic. > > I still think it would be possible to use a combination of a > Makefile rule and GNU make features to spit out a list of targets and > their dependet .h and .c files. I wouldn't mind if someone was willing to add and maintain this, of course, but at least for me it wouldn't be particularely useful. Cheers, Thomas Berg -- 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