Hi, On Tue, 18 Aug 2009, Daniel Barkalow wrote: > On Tue, 18 Aug 2009, Marius Storm-Olsen wrote: > > > Johannes Schindelin said the following on 18.08.2009 16:11: > > > On Tue, 18 Aug 2009, Marius Storm-Olsen wrote: > > > > So, instead of rely on these vcproj files which *will* go stale, > > > > we can simply use the same Makefile system which everyone else is > > > > using. :) After all, we're just compiling with a different > > > > compiler. The end result will still rely on the *msysGit > > > > environment* to function, so we already require it. Thus, GNU Make > > > > is present, and we can use it. > > > > > > We can also use sed or perl to generate/modify the .vcproj files, or > > > run CMake (once Pau got it to build), and package the stuff using > > > zip (once I got that to build). > > > > Really? That would be some script being able to parse the Makefile, > > and create something reasonable as a vcproj script :) Keeping all the > > options in sync, conditional files/libs, all the various end > > executables (a separate .vcproj for each of them, and a solution file > > (.sln)to tie them all together into a .. "solution", a complete > > product blah blah blah) etc. > > I think it wouldn't be impossible to split the Makefile into an > easy-to-parse part and an irrelevant-to-vcproj part. What? That is pretty fragile. It would be _much_ better to just add another Makefile target that outputs the files needed for the targets. We do not need to keep the Makefile as-is! If the change is not intrusive, I am sure our friendly maintainer will not see a problem either. No need for fragile parsing at all. 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