From: Philip Oakley <philipoakley@iee.org>
To: GitList <git@vger.kernel.org>
Cc: Marius Storm-Olsen <mstormo@gmail.com>,
Ramsay Jones <ramsay@ramsay1.demon.co.uk>,
Jonathan Nieder <jrnieder@gmail.com>,
Michael Wookey <michaelwookey@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Msysgit <msysgit@googlegroups.com>
Subject: [RFC 4/4] Improve layout and reference msvc-build script
Date: Thu, 20 Nov 2014 23:38:02 +0000 [thread overview]
Message-ID: <1416526682-6024-5-git-send-email-philipoakley@iee.org> (raw)
In-Reply-To: <1416526682-6024-1-git-send-email-philipoakley@iee.org>
Layout the 'either/or' with more white space to clarify
which alternatives are matched up.
Reference the build script which automates one sequence of options.
Signed-off-by: Philip Oakley <philipoakley@iee.org>
---
compat/vcbuild/README | 29 +++++++++++++++++++++--------
1 file changed, 21 insertions(+), 8 deletions(-)
diff --git a/compat/vcbuild/README b/compat/vcbuild/README
index df8a657..f4f6723 100644
--- a/compat/vcbuild/README
+++ b/compat/vcbuild/README
@@ -3,20 +3,24 @@ The Steps of Build Git with VS2008
1. You need the build environment, which contains the Git dependencies
to be able to compile, link and run Git with MSVC.
- You can either use the binary repository:
+ You can either:
+ use the binary repository:
WWW: http://repo.or.cz/w/msvcgit.git
Git: git clone git://repo.or.cz/msvcgit.git
Zip: http://repo.or.cz/w/msvcgit.git?a=snapshot;h=master;sf=zip
- and call the setup_32bit_env.cmd batch script before compiling Git,
- (see repo/package README for details), or the source repository:
+ and call the setup_32bit_env.cmd batch script before compiling Git,
+ (see repo/package README for details),
+
+ or:
+ use the source repository:
WWW: http://repo.or.cz/w/gitbuild.git
Git: git clone git://repo.or.cz/gitbuild.git
Zip: (None, as it's a project with submodules)
- and build the support libs as instructed in that repo/package.
+ and build the support libs as instructed in that repo/package.
2. Ensure you have the msysgit environment in your path, so you have
GNU Make, bash and perl available.
@@ -33,18 +37,27 @@ The Steps of Build Git with VS2008
make common-cmds.h
to generate the common-cmds.h file needed to compile git.
-4. Then either build Git with the GNU Make Makefile in the Git projects
- root
+4. Then either
+
+ build Git with the GNU Make Makefile in the Git projects root
make MSVC=1
- or generate Visual Studio solution/projects (.sln/.vcproj) with the
+ or
+
+ generate Visual Studio solution/projects (.sln/.vcproj) with the
command
perl contrib/buildsystems/generate -g Vcproj
and open and build the solution with the IDE
devenv git.sln /useenv
- or build with the IDE build engine directly from the command line
+ or
+
+ build with the IDE build engine directly from the command line
devenv git.sln /useenv /build "Release|Win32"
The /useenv option is required, so Visual Studio picks up the
environment variables for the support libraries required to build
Git, which you set up in step 1.
Done!
+
+Or, use the msvc-build script; also in /msysgit/bin/msvc-build
+
+For those with VS2010: You may need to associate the generated .sln file with VS2010 rather than the MS version selector program.
--
1.9.4.msysgit.0
--
--
*** Please reply-to-all at all times ***
*** (do not pretend to know who is subscribed and who is not) ***
*** Please avoid top-posting. ***
The msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.
You received this message because you are subscribed to the Google
Groups "msysGit" group.
To post to this group, send email to msysgit@googlegroups.com
To unsubscribe from this group, send email to
msysgit+unsubscribe@googlegroups.com
For more options, and view previous threads, visit this group at
http://groups.google.com/group/msysgit?hl=en_US?hl=en
---
You received this message because you are subscribed to the Google Groups "Git for Windows" group.
To unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2014-11-20 23:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 23:37 [RFC 0/4] Fix the Visual Studio 2008 .sln generator Philip Oakley
2014-11-20 23:37 ` [RFC 1/4] Fix i18n -o option in msvc engine.pl Philip Oakley
2014-11-21 9:41 ` Johannes Schindelin
2014-11-21 20:27 ` Philip Oakley
2014-11-20 23:38 ` [RFC 2/4] Properly accept quoted space in filenames Philip Oakley
2014-11-21 9:42 ` Johannes Schindelin
2014-11-21 22:34 ` Junio C Hamano
2014-11-21 23:11 ` Philip Oakley
2014-11-21 23:21 ` Junio C Hamano
2014-11-20 23:38 ` [RFC 3/4] engine.pl: split the .o and .obj processing Philip Oakley
2014-11-21 9:48 ` Johannes Schindelin
2014-11-21 20:35 ` Philip Oakley
2014-11-23 15:28 ` Johannes Schindelin
2014-11-23 22:50 ` Philip Oakley
2014-11-20 23:38 ` Philip Oakley [this message]
2014-11-21 9:51 ` [RFC 4/4] Improve layout and reference msvc-build script Johannes Schindelin
2014-11-21 21:05 ` Philip Oakley
2014-11-21 9:38 ` [RFC 0/4] Fix the Visual Studio 2008 .sln generator Johannes Schindelin
2014-11-21 20:22 ` Philip Oakley
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=1416526682-6024-5-git-send-email-philipoakley@iee.org \
--to=philipoakley@iee.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=michaelwookey@gmail.com \
--cc=mstormo@gmail.com \
--cc=msysgit@googlegroups.com \
--cc=ramsay@ramsay1.demon.co.uk \
/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).