git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 4/5] vcbuild/readme: Improve layout and reference msvc-build script

From
Philip Oakley <philipoakley@iee.org>
Date
Dec 24, 2014, 10:47 UTC
Message-ID
<1419418034-6276-5-git-send-email-philipoakley@iee.org>
In-Reply-To
<1419418034-6276-1-git-send-email-philipoakley@iee.org>

Layout the 'either/or' with more white space to clarify which alternatives are matched up.

Reference the Msysgit build script which automates one sequence of options.
Signed-off-by: Philip Oakley <philipoakley@iee.org>
---
 compat/vcbuild/README | 27 +++++++++++++++++++--------
 1 file changed, 19 insertions(+), 8 deletions(-)
diff --git a/compat/vcbuild/README b/compat/vcbuild/README
index df8a657..7548dc4 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,25 @@ 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 Msysgit msvc-build script; available from that project.
-- 
2.1.0
Previous: Philip OakleyNext: Philip Oakley
Message 6 of 8 in “Fix the Visual Studio 2008 .sln generator”
  1. 0/5 Fix the Visual Studio 2008 .sln generatorPhilip Oakley, Dec 24, 2014
  2. 1/5 engine.pl: Fix i18n -o option in msvc buildsystem generatorPhilip Oakley, Dec 24, 2014
  3. Philip OakleyDec 26, 2014
  4. 2/5 engine.pl: Properly accept quoted spaces in filenamesPhilip Oakley, Dec 24, 2014
  5. 3/5 engine.pl: ignore invalidcontinue.obj which is known to MSVCPhilip Oakley, Dec 24, 2014
  6. 4/5 vcbuild/readme: Improve layout and reference msvc-build scriptPhilip Oakley, Dec 24, 2014
  7. 5/5 engine.pl: provide more debug print statementsPhilip Oakley, Dec 24, 2014
  8. Philip OakleyDec 26, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.