From: John F. <jo...@ti...> - 2002-09-02 18:18:22
|
This is all perhaps correct if you substitute 'gcc' for 'MinGW' in Greg's text below. I think Alex's original question was about which packages to download, as they are named on the sourceforge site. As Max pointed out, the 'MinGW' package contains binutils + gcc + mingw-runtime + w32api. Therefore there is no such thing as 'MinGW only'. 'MinGW' contains it all, but was assembled as a convenience to new users some time ago. If you download MinGW you will get the last stable version of gcc, plus somewhat out of date versions of mingw-runtime and w32api. Max's suggestion on what individual packages to download is good, to get the latest bug fixes in mingw-runtime and w32api: binutils-2.13-20020808-1.tar.gz binutils-2.13-info-html.tar.gz gcc-2.95.3-20010828.tar.gz mingw-runtime-2.1.tar.gz w32api-2.0.tar.gz Greg Chicares wrote: > Alex Vinokur wrote: > >>What can we do >> > > I feel fairly confident about these guesses, and very > certain that someone will correct them if they're wrong. > > >>* with MinGW only >> > > Compile programs that don't use the C standard library, > such as > int main(){} > But if you want to link them, I think you need binutils. > > >>* with MinGW and mingw-runtime >> > > Compile programs that use the C standard library, like > #include <iostream> > int main(){std::cout << "Hello world.\n";} > > With the latest versions, some C++ headers include other > headers from w32api as well. > > >>* with MinGW and w32api >> > > Compile programs that use the 32-bit windows API: perhaps > #include <windows.h> > int main(){MessageBeep(MB_ICONQUESTION);} > > I didn't reconfigure my computer to validate any of these > examples. > > >>* with mingw-runtime only >>* with w32api only ? >> > > Very little. These are just headers and import libraries. |