MinGW

MinGW
Original author(s) Colin Peters
Developer(s) MinGW Project
Initial release July 1, 1998 (1998-07-01)
Stable release
0.6.2 - beta[1] / October 4, 2013 (2013-10-04)
Written in C, C++
Operating system Microsoft Windows, Unix-like (as a cross compiler)
Type Compiler
License Public domain (headers), GNU General Public License (compiler and toolchain)
Website mingw.org

MinGW (Minimalist GNU for Windows), formerly mingw32, is a free and open source software development environment for creating Microsoft Windows applications.

It includes a port of the GNU Compiler Collection (GCC), GNU Binutils for Windows (assembler, linker, archive manager), a set of freely distributable Windows specific header files and static import libraries which enable the use of the Windows API, a Windows native build of the GNU Project's GNU Debugger, and miscellaneous utilities.

MinGW does not rely on third-party C runtime dynamic-link library (DLL) files, and because the runtime libraries are not distributed using the GNU General Public License (GPL), it is not necessary to distribute the source code with the programs produced, unless a GPL library is used elsewhere in the program.[2]

MinGW can be run either on the native Microsoft Windows platform, cross-hosted on Linux (or other Unix), or "cross-native" on Cygwin.

An alternative called MinGW-w64 was created by a different author to include several new APIs and provide 64-bit support.

History

MinGW was originally called mingw32 (Minimalist GNU for W32), following the GNU convention whereby Windows is shortened as "W32".[3][4] The numbers were dropped in order to avoid the implication that it would be limited to producing 32-bit binaries. Colin Peters authored the initial release in 1998, consisting only of a Cygwin port of GCC.[5][6] Jan-Jaap van der Heijden created a Windows-native port of GCC and added binutils and make.[5][6] Mumit Khan later took over development, adding more Windows-specific features to the package, including the Windows system headers by Anders Norlander.[5][6] In 2000, the project was moved to SourceForge.net in order to solicit more assistance from the community and centralize its development.[5][6]

MinGW was selected as Project of the Month at SourceForge.net for September 2005.[6]

In the last quarter of 2013 a new project was started,[7] MSYS2 together with 32-bit and 64-bit MinGW packages. This project was created to keep track with newer advances of the Cygwin project and the fact that the original MSYS was not able to keep up with Cygwin. MSYS2 is an independent rewrite of MSYS, based on modern Cygwin (POSIX compatibility layer) and MinGW-w64 with the aim of better interoperability with native Windows software. It uses Arch Linux's Pacman as the package manager.

Programming language support

Most languages supported by GCC are supported on the MinGW port as well. These include C, C++, Objective-C, Objective-C++, Fortran and Ada. The GCC runtime libraries are used (libstdc++ for C++, libgfortran for Fortran, etc.).

MinGW links by default to the Windows OS component library MSVCRT, which is the C library that Visual C version 6.0 linked to (the initial target was CRTDLL), which was released in 1998 and therefore does not include support for C99 features, or even all of C89. While targeting MSVCRT yields programs that require no additional runtime redistributables to be installed, the lack of support for C99 has caused porting problems, particularly where printf-style conversion specifiers are concerned. These issues have been partially mitigated by the implementation of a C99 compatibility library, libmingwex, but the extensive work required is far from complete and may never be fully realized.[8] MinGW-w64 has resolved these issues, and provides fully POSIX compliant printf functionality.

Components

The MinGW project maintains and distributes a number of different core components and supplementary packages, including various ports of the GNU toolchain, such as GCC and binutils, translated into equivalent packages.[9][10] These utilities can be used from the Windows command line or integrated into an IDE. Packages may be installed using the command line via mingw-get.[11]

MinGW supports dynamic libraries named according to the <name>.lib and <name>.dll conventions, as well as static libraries following the lib<name>.a naming convention common on Unix and Unix-like systems.

In addition, a component of MinGW known as MSYS (minimal system) provides Windows ports of a lightweight Unix-like shell environment including rxvt and a selection of POSIX tools sufficient to enable autoconf scripts to run,[12] but it does not provide a C compiler or a case-sensitive file system.[13]

mingwPORTs are user contributed additions to the MinGW software collection. Rather than providing these "add-ons" as precompiled binary packages, they are supplied in the form of interactive Bourne shell scripts, which guide the end user through the process of automatically downloading and patching original source code, then building and installing it. Users who wish to build any application from a mingwPORT must first install both MinGW and MSYS.[14]

The implementation of Windows system headers and static import libraries are released under a permissive license,[15] while the GNU ports are provided under the GNU General Public License. Binary downloads of both the complete MSYS package and individual MinGW GNU utilities are available from the MinGW site.

Comparison with Cygwin

MinGW was forked from version 1.3.3 of Cygwin.[5] Although both Cygwin and MinGW can be used to port Unix software to Windows, they have different approaches:[16] Cygwin aims to provide a complete POSIX layer comprising a full implementation of all major Unix system calls and libraries. Compatibility is considered higher priority than performance. On the other hand, MinGW's priorities are simplicity and performance. As such, it does not provide certain POSIX APIs which cannot easily be implemented using the Windows API, such as fork(), mmap() and ioctl().[16] Applications written using a cross-platform library that has itself been ported to MinGW, such as SDL, wxWidgets, Qt, or GTK+, will usually compile as easily in MinGW as they would in Cygwin.

Windows programs written with Cygwin run on top of a copylefted compatibility DLL that must be distributed with the program, along with the program's source code. MinGW does not require a compatibility layer, since MinGW-based programs are compiled with direct calls to Windows APIs.

The combination of MinGW and MSYS provides a small, self-contained environment that can be loaded onto removable media without leaving entries in the registry or files on the computer. Cygwin Portable provides a similar feature that is far more robust.

It is also possible to cross-compile Windows applications with MinGW-GCC under POSIX systems. This means that developers do not need a Windows installation with MSYS to compile software that will run on Windows with or without Cygwin.

MinGW-w64

MinGW-w64
Original author(s) OneVision Software
Developer(s) Kai Tietz
Initial release 2005 (2005)
Stable release
6.2.1[17] / September 5, 2016 (2016-09-05)
Written in C, C++
Operating system Microsoft Windows
Type Compiler
License Public domain (headers), GNU General Public License (compiler and toolchain), Zope Public License
Website mingw-w64.org

In 2005, MinGW-w64, was created by OneVision Software under clean room design principles, since the original MinGW project was not prompt on updating its code base, including the inclusion of several key new APIs and the much needed 64-bit support. In 2008, OneVision then donated the code to Kai Tietz, one of its lead developers, under the condition that it remain open source.[18] It was first submitted to the original MinGW project, but refused under suspicion of using non-public or proprietary information.[19] For many reasons, the lead developer and co-founder of the MinGW-w64 project, Kai Tietz, decided not to attempt further cooperation with MinGW.[20]

MinGW-w64 provides a more complete Win32 API implementation,[21] including:

Additionally, the MinGW-w64 project maintains winpthreads, a wrapper library similar to pthreads-win32, with the main difference that it allows GCC to use it as a threads library resulting in functional C++11 thread libraries <thread>, <future>, and <mutex>.

See also

References

  1. ↑ "Recent Project News". mingw.org.
  2. ↑ "(MinGW on) MinGW". MinGW.org/wiki. 2008-07-07. Retrieved 2013-10-16.
  3. ↑ "GNU Coding Standards". gnu.org. Free Software Foundation. April 27, 2013. 5.5 Portability between System Types. Retrieved July 1, 2013.
  4. ↑ Stallman, Richard (2000-09-18). "Libtool Re: Naming a project gnu-win32?". libtool (Mailing list). Retrieved 2013-05-21.
  5. 1 2 3 4 5 "(MinGW's) History". MinGW.org. Retrieved 2012-07-09.
  6. 1 2 3 4 5 "(sourceforge's) Project of the Month". SourceForge.net. 2005-08-31. Retrieved 2012-07-09.
  7. ↑ "How are msys, msys2, and msysgit related to each other?". stackoverflow.com. Retrieved 2015-04-01.
  8. ↑ "(MinGW And) C99". MinGW.org/wiki. 2010-06-21.
  9. ↑ "(MinGW) FAQ". MinGW.org. Retrieved 2012-07-09.
  10. ↑ "MinGW - Minimalist GNU for Windows". Sourceforge.net. Retrieved 2012-07-09.
  11. ↑ "MinGW Command Line Interface Installer". Retrieved 14 June 2012.
  12. ↑ "(wiki:) MSYS". MinGW.org. Retrieved 2016-02-18.
  13. ↑ "(wiki:) MSYS". MinGW.org. Retrieved 2016-02-18. A common misunderstanding is MSYS is "UNIX on Windows", MSYS by itself does not contain a compiler or a C library, [...] nor does it provide any UNIX specific functionality like case-sensitive filenames.
  14. ↑ "(wiki:) mingwPORT". MinGW.org. Retrieved 2012-07-09.
  15. ↑ "(MinGW) Licensing Terms". MinGW.org. Retrieved 2012-07-09.
  16. 1 2 "(MinGW:) About Cygwin". MinGW.org. Retrieved 2012-07-09.
  17. ↑ "MinGW-w64 - ... (directory listing releases)". mingw-w64.org. Retrieved 2016-11-27.
  18. ↑ "(MinGW-w64) History". MinGW-w64 Wiki. Retrieved 2016-02-18.
  19. ↑ Marshall, Keith (19 July 2009). "Re: Harmonizing mingwrt / w32api with mingw-w64". MinGW-dvlpr (Mailing list). Retrieved 12 June 2014. However, we would require a formal audit of mingw-64 code, to ensure conformance with our requirements for truly open documentation of sources, before [merge of mingw-w64] could be completed.
  20. ↑ Tietz, Kai (20 July 2014). "Re: Harmonizing mingwrt / w32api with mingw-w64". MinGW-dvlpr (Mailing list). Retrieved 12 June 2014.
  21. ↑ "MinGW-w64". MinGW-w64.org. Retrieved 30 May 2013.
This article is issued from Wikipedia - version of the 11/29/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.