The Git for Windows SDK for Git for Windows contributors.7z archive, and can be generated using the files in portable/. This installer is actually a self-extracting. Portable Git for Windows for end users ("USB drive edition").The subdirectory installer/ contains the files to generate this installer. The Git for Windows project aims to provide three different types of installers: Before the first MSYS2 package is built, the prerequisite development packages have to be installed by executing pacman -Sy base-devel binutils. To build the packages inside the /usr/src/MSYS2-packages/ directory, the user has to launch a special shell by double-clicking the msys2_shell.bat script in the top-level directory of the Git SDK, switch the working directory to the appropriate subdirectory of /usr/src/MSYS2-packages/ and then execute makepkg -s. The MinGW packages are built from the MINGW-packages repository which can be initialized in the Git SDK Bash via As a consequence, the Git for Windows project tries to provide as many components as possible as MinGW binaries. The POSIX emulation layer of MSYS2 binaries is convenient, but comes at a cost: Typically, MSYS2 programs are noticably slower than their MinGW counterparts (if there are such counterparts). Examples: cURL (a library to talk to remote servers via HTTP(S), (S)FTP, etc), emacs, Inkscape, etc MinGW stands for "Minimal GNU for Windows". MinGW refers to libraries and programs that are compiled using GNU tools but do not require any POSIX semantics, instead relying on the standard Win32 API and the C runtime library. Bash and Perl are examples of MSYS2 programs. It is very easy to port libraries and programs from Unix/Linux because most of the POSIX semantics is emulated reasonably well, for example the fork() function. MSYS2 refers to the libraries and programs that use the POSIX emulation layer ("msys2 runtime", derived from Cygwin's cygwin1.dll). To support those scripts, Git for Windows uses MSYS2, a project providing a minimal POSIX emulation layer (based on Cygwin), a package management system (named "Pacman", borrowed from Arch Linux) and a number of packages that are kept up-to-date by an active team of maintainers, including Bash, Perl, Subversion, etc. Some parts (not supported by Git for Windows yet) are written in other script languages, still. Git is not a monolithic executable, but consists of a couple of executables written in C, a couple of Bash scripts, a couple of Perl scripts, and a couple of Tcl/Tk scripts. The idea is that the Git for Windows repository serves as a test bed to develop patches and patch series that are specific to the Windows port, and once the patches stabilized, they are submitted upstream. The Git for Windows project maintains a friendly fork of the "upstream" Git project. The most important part of Git for Windows is Git, obviously. you can run it without installing, from wherever it was unpacked). The build environment brings all the necessary parts required to build a Git for Windows installer, or a portable Git for Windows ("portable" = "USB drive edition", i.e. Git checkout main Components of the Git for Windows SDK
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |