Posted July 25th, by Mingwadmin
- Getting Started
- Install
- MinGW
Automated Installer
If you were new to MinGW, see the MinGW Getting Started instructions to use the automated GUI or manual CLI (Command line I Nterface) installers. What follows below is instructions for a very ' manual ' download, typically only attempted by more experienced users.
Manual Installation
Before you start this manual installation, read the release notes (at the bottom of the page).
- Determine which files below you need and download them.
- Extract the files into a directory such as C:\MinGW
- ADD C:\MinGW\bin; To the PATH environment variable.
You'll need a program so can extract. Tar.lzma files, such as 7-zip or one that provides command-line tar and Lzma too Ls. A Basic Standalone Tar program, includes LZMA support is available from the MinGW project and is called Bsdtar.
You must add C:\MinGW\bin; To your user PATH environment variable manually. You can permanently add C:\MinGW\bin; To your PATH by following the instructions in the ' Environment Settings ' section on the MinGW Getting Started Pag E.
The resulting C:\MinGW subtree is fully relocatable which means so can have multiple installations or versions of th E MinGW Suite. You can potentially has installations such as:
C:\MinGW-3.4.5C:\MinGW-4.8.1etc.
Switching between these is merely a matter of renaming any particular directory to C:\MinGW.
Files to Get
Download at least the following (or newer) packages from the MinGW Download Page. Where the or more component packages is indicated, you need both / all of them.
- Binutils (BIN)
- Mingw-runtime (Dev and DLL)
- W32api
- Required Runtime libraries for GCC:
- MPC (DLL)
- MPFR (DLL)
- GMP (DLL)
- Pthreads (Dev and DLL)
- Iconv (DLL)
- Zlib
- GetText
- Gcc-core (Bin and Dev and dll)
The above is the minimum requirements for a working C Language compiler using the MinGW GCC toolchain. The support libraries (MPC, MPFR, and GMP) provide also "dev" packages, but those is only needed if you want to link your program against those libraries. (You do need the ' dev ' package for pthreads, since link commands that use-pthread need to link against this library.) Likewise, the Binutils package provides a "dev" package that includes libraries, such as LIBIBERTY.A and LIBBFD.A, and the corresponding headers; Wish to install those if you want to develop programs that is linked against those libraries. If you don't find the linker scripts in the Binutils "bin" package, they might is in the "dev" package.
You can also add one or more of the following optional compilers or tools. Choose to install, need all three of the bin, the dev and the DLL com Ponent Packages:
- Gcc-c++ (Bin and Dev and dll) for C + +
- GCC-OBJC (Bin and Dev and dll) for Objective C
- Gcc-fortran (Bin and Dev and dll) for Fortran 90/95
- Gcc-java (not yet available) for Java
- Gcc-ada (Bin and Dev and dll) for ADA
Note that the GCC versions of these files must match the GCC version of the Gcc-core installed.
You can also add the following additional utilities:
- Mingw-gdb and Libexpat for debugger
- Mingw32-make for Make
- Mingw-utils for MinGW Utilities
- MSYSDTK for Unix-style Developer Toolkit
- MSYS for Unix-style commands and Shell. (See the MSYS page for installation instructions.)
Also want the following features:
- Translations of GCC, binutils, GDB, and make messages to languages other than 中文版
- Documentation for Gcc-core, gcc-c++, and Gcc-fortran
Getting Updates or Making changes
Updating a single package (e.g-there is a new version of W32API) can-do by extracting the new version to C:\Min GW to overwrite the older version. This manual update also works with an initial automated install.
"Original: Http://www.mingw.org/wiki/InstallationHOWTOforMinGW"
HOWTO Install the MinGW (GCC) Compiler Suite