The version of msysGit that ships with GitHub for Windows
Перейти к файлу
ADTC c00ce10aa3 Add fallback section for delayed expansion unavailability
Taking cue from start-ssh-agent.cmd, enhanced gitk.cmd to fallback to
the immediate expansion script if delayed expansion is unavailable.

Both script sections are the same, except for the different environment
variable delimiters. When new changes are made, both sections must be
updated correctly, taking care to use the correct delimiter (! or %) to
demarcate the environment variables. (In fact, the fallback section is
exactly the same as the original script before previous commit.)

Signed-off-by: ADTC <send2adtc@gmail.com>
2014-09-15 18:12:08 +08:00
bin fix DLL relocation problem with recompiled SVN libs 2014-08-15 21:12:44 +02:00
cmd Add fallback section for delayed expansion unavailability 2014-09-15 18:12:08 +08:00
doc
etc
git@9745bbe6d5 Commit submodule in preparation of 1.9.4 2014-08-15 18:20:18 +02:00
include
lib Update openssl to 1.0.1i 2014-08-14 13:29:43 +02:00
libexec Add openssh files compiled against new openssl 1.0.1h 2014-08-05 16:05:38 +02:00
mingw Install OpenSSL 0.9.8zb header files 2014-08-13 13:42:02 +02:00
share Installer: Default to automatically close and restart apps in silent mode 2014-08-29 00:05:42 +02:00
src Update to changed sourceforge API urls 2014-08-14 17:07:23 +02:00
ssl
.gitattributes
.gitignore
.gitmodules
README.md
THIS_IS_MSYSGIT
Vagrantfile
git-cmd.bat
msys.bat
wine-start.sh

README.md

Build environment for Git for Windows

This is the build environment -- also known as msysGit -- for Git for Windows.

The easiest way is to install it via the net installer. This installer will clone our two repositories, including all the necessary components to build Git for Windows, and perform an initial build.

The build environment

msysGit brings a few components that are required to build Git:

  • Bash, a Unix-type command-line shell. Quite a few components of Git itself are still shell scripts. Therefore, Bash is required to execute Git commands (see the output of cd /git && git ls-files \*.sh for a full list).
  • the GNU C Compiler. Since we try to rely only on free software (apart from the Operating System, of course), we think it makes more sense to rely on GCC than on Visual Studio express. Also, it makes the maintenance burden lighter, as upstream Git also targets mainly GCC.
  • GNU Make.
  • Perl. Still required for a couple of Git components (see the output of cd /git && git ls-files \*.perl), most notably git svn.
  • Tcl/Tk, a scripting language making it easy to implement cross-platform graphical user interfaces. We need this for gitk and git gui.
  • cURL, a library implementing HTTP and FTP transport.
  • many more libraries.
  • some Unix programs required by the shell scripts in Git.

The relationship between msysGit and Git for Windows

Git for Windows is the software package that installs a minimal environment to run Git on Windows. It comes with a Bash (a Unix-type shell), with a Perl interpreter and with the Git executable and its dependencies.

On the other hand, msysGit is the software package installing the build environment that can build Git for Windows. The easiest way is to install it via the net installer.

The difference between MSys and MinGW

The MinGW project's goal is to provide a way to compile native Windows binaries with no POSIX layer using the GNU C Compiler.

However, at least the Bash needs a POSIX layer (most notably due to the absence of the fork() call on Windows). Therefore, MSys (the minimal system) is thrown in, offering the minimal system necessary to offer Bash (and Perl) functionality on Windows.

Consequently, MSys ships with a POSIX layer (based on an old version of Cygwin) that is only used by the Bash and Perl, but not by anything compiled within that environment.

Further information

For more information and documentation, please have a look and enhance our Wiki.

For code contributions and discussions, please see our mailing list.