From: "Philip Oakley" <philipoakley@iee.org>
To: "Andrew Ardill" <andrew.ardill@gmail.com>,
"Vincent van Ravesteijn" <vfr@lyx.org>
Cc: "Git MsysGit" <msysgit@googlegroups.com>, <git@vger.kernel.org>
Subject: Re: Compiling on Windows
Date: Wed, 19 Oct 2011 22:46:34 +0100 [thread overview]
Message-ID: <2015B7F2CEAE4B449EA4EF744F9B8FD9@PhilipOakley> (raw)
In-Reply-To: 4E9E811C.10205@lyx.org
From: "Vincent van Ravesteijn" <vfr@lyx.org>
> Op 18-10-2011 6:08, Andrew Ardill schreef:
>> Hi list, I have been searching for details on what is required to
>> compile on Windows, but haven't found anything conclusive. Perhaps
>> there is something on the wiki, but unfortunately it is down at the
>> moment.
>>
>> Can anyone point me in the right direction? I would like to be able to
>> compile and test topic branches, and perhaps even do some dev work on
>> my windows machine.
>
> I once wrote a little step-by-step tutorial on how to compile the native
> Windows Git with MSVC (Express).
>
> http://blog.vfrconsultancy.nl/#post0
The blog post filled in a few gaps in the Msysgit README instructions about
where to place the various downloads described.
>
> Be aware that git runs without apparent problems, but that all
> functionality written in shell scripts can't be used.
>
> HTH,
>
> Vincent
> --
Many thanks, it saved me asking.
Philip
next prev parent reply other threads:[~2011-10-19 21:46 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
2011-10-18 6:39 ` Alexey Shumkin
2011-10-19 7:49 ` Vincent van Ravesteijn
2011-10-19 21:46 ` Philip Oakley [this message]
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=2015B7F2CEAE4B449EA4EF744F9B8FD9@PhilipOakley \
--to=philipoakley@iee.org \
--cc=andrew.ardill@gmail.com \
--cc=git@vger.kernel.org \
--cc=msysgit@googlegroups.com \
--cc=vfr@lyx.org \
/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