Re: [PATCH 10/11] Add MSVC Project file
- From
- Pau Garcia i Quiles <pgquiles@elpauer.org>
- Date
- Aug 17, 2009, 22:19 UTC
- Message-ID
- <3af572ac0908171519h7b72427lba7536506d44460e@mail.gmail.com>
- In-Reply-To
- <alpine.DEB.1.00.0908180005250.8306@pacific.mpi-cbg.de>
On Tue, Aug 18, 2009 at 12:10 AM, Johannes Schindelin<Johannes.Schindelin@gmx.de> wrote:
Show 28 quoted lines
> Hi, > > On Mon, 17 Aug 2009, Pau Garcia i Quiles wrote: > >> On Mon, Aug 17, 2009 at 11:05 PM, Johannes >> Schindelin<Johannes.Schindelin@gmx.de> wrote: >> >> > You are putting an undue burden on the already overloaded maintainer. >> >> Sorry, but I'm a bit lost now. What maintainer are we talking about now? >> Junio? > > I was talking about me, as maintainer of msysGit. > >> As I would be providing a turn-key CMake build system, the only burden I >> would be putting on the maintainer would be learning CMake. >> >> Given that I'm providing a comprehensive (100+ slides) CMake tutorial >> ( http://www.elpauer.org/stuff/learning_cmake.pdf ) , which I use in >> my CMake workshops, I think I'm making that burden a bit lighter. >> >> If the next git conference is somewhere in Europe, I could also fly >> there and we'd have a CMake tutorial, if people would feel more >> comfortable that way. > > This is exactly what I mean by burden. Why do I have to learn a new > system, and suffer the hassle of integrating it into the current build > system, which works quite well thankyouverymuch?
Because it works for every platform, including Visual C++, where a Bourne shell is not available and where you currently need to maintain a different built system.
Show 32 quoted lines
> Never run a changing system. > >> > Well, let's see if you can provide a /src/cmake/release.sh that >> > compiles CMake from scratch, and _then_ I'll look into CMake again. >> >> Again, I'm a bit lost. What '/src/cmake/release.sh' are we talking about >> now? Would that be part of CMake or git ? > > Maybe this: > > http://article.gmane.org/gmane.comp.version-control.git/126286 > > and this: > > http://repo.or.cz/w/msysgit.git?a=blob;f=src/curl/release.sh;h=d7516cbf6e92af4de138ce405d88561fbe1e92a8;hb=968336eddac1874c56cd934d10783566af5a3e26 > > helps. > > To quote myself (as you appear to have missed 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.
Hmmm indeed I have missed a lot, thanks. A lot of what you had written in other e-mails was being hidden by GMail as "quoted" text :-/
It seems we are talking about two different things here. I'm talking about getting the CMake-based build system in git.git, you are talking about msysgit. If getting into msysgit is the first step to getting into git.git, I'll start from msysgit. Are the differences between both branches so big they cannot be merged into a single branch yet ?
> Short form: if you make it easy for me, I will look at it again, if you > make it hard on me, you will just have done to me what you now try > to avoid yourself: wasted time.
Let's see what I can do.
-- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer)