Hi, On Tue, 18 Aug 2009, Marius Storm-Olsen wrote: > Johan 't Hart said the following on 18.08.2009 19:41: > > Junio C Hamano schreef: > > > Since use of make implies use of shell, this makes me wonder if it > > > would make sense to go one step further by giving msvc users a thin > > > shell wrapper mcvc-cc that turns bog-standard cc command line into > > > whatever cl uses. > > > > Just using the msvc toolchain for building git misses the whole > > purpose of what VC is used for. MSVC would be used because of the > > IDE, not for the compiler IMO. > > Bull. MSVC produces superior code on Windows compared to MinGW, I'm afraid. > Add the /LTGC (Link Time Code Generation), and MSVC generates very good cross > compile-unit optimized code. (I know gcc has the option, but it's not as good, > by far) > Coupled now with built-in static code analysis, these are only two reasons why > *I* would want to build it directly from the command line without worrying > that my .vcproj is out-of-sync with the main development. > You can still debug with the MSVC debugger if you'd like, and the MSVC IDE > allows you to wrap Makefile project too, so you can *still* use the IDE.. Well, "you can *still* use the IDE" is a bit exaggerated, no? At least unless you misunderstand "IDE" to mean "Integrated Debugging environment". You'll lose not only the ability to follow definitions/declarations in the code, you'll also lose the ability to compile incrementally _while_ debuggin, and Visual Studio's feature to move to the next/previous compile error. 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