From: Sebastian Schuberth <sschuberth@gmail.com>
To: kusmabite@gmail.com
Cc: Andrew Ardill <andrew.ardill@gmail.com>,
Frans Klaver <fransklaver@gmail.com>,
git@vger.kernel.org
Subject: Re: Compiling on Windows
Date: Tue, 18 Oct 2011 18:07:20 +0200 [thread overview]
Message-ID: <4E9DA438.2020903@gmail.com> (raw)
In-Reply-To: <CABPQNSZhWOa5wken4vh6Hcza8EM4VnekE3VUFJNmaEJvWME=ew@mail.gmail.com>
On 18.10.2011 16:02, Erik Faye-Lund wrote:
>> there. Foolishly, I had glossed over the msysgit installers on the
>> project home (I think I thought they were Git for Windows installers).
>
> Yeah, the installer sets up a fully self-contained MSYS-based
> development environment to hack on Git for Windows.
I keep advertizing my mingwGitDevEnv [1] project which aims to become an alternative to the current msysGit net installer [2]. The advantage of mingwGitDevEnv will be that it comes with an mingw-get based environment, i.e. you can very easily update / add new MinGW / MSYS tools directly from upstream.
Just today I reached a state were mingwGitDevEnv can successfully build git.exe, but git-gui etc. are still missing due to a lack of mingw-get compatible Tcl/Tk packages.
[1] https://github.com/sschuberth/mingwGitDevEnv
[2] http://msysgit.googlecode.com/files/msysGit-netinstall-1.7.7-preview20111014.exe
--
Sebastian Schuberth
next prev parent reply other threads:[~2011-10-18 16:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 4:08 Compiling on Windows Andrew Ardill
2011-10-18 5:41 ` Frans Klaver
2011-10-18 6:17 ` Andrew Ardill
2011-10-18 14:02 ` Erik Faye-Lund
2011-10-18 16:07 ` Sebastian Schuberth [this message]
2011-10-18 6:39 ` Alexey Shumkin
2011-10-19 7:49 ` Vincent van Ravesteijn
2011-10-19 21:46 ` Philip Oakley
2011-10-19 23:17 ` [msysGit] " Johannes Schindelin
2011-10-20 7:06 ` Philip Oakley
2011-10-20 21:38 ` Vincent van Ravesteijn
2011-10-21 11:41 ` Erik Faye-Lund
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E9DA438.2020903@gmail.com \
--to=sschuberth@gmail.com \
--cc=andrew.ardill@gmail.com \
--cc=fransklaver@gmail.com \
--cc=git@vger.kernel.org \
--cc=kusmabite@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).