Community
Participate
Working Groups
Build ID: 7.0rc2 Help URL: http://127.0.0.1:1089/help/topic/org.eclipse.cdt.doc.user/concepts/cdt_c_before_you_begin.htm I assume it should point to MinGW-5.1.6.exe http://sunet.dl.sourceforge.net/project/mingw/Automated%20MinGW%20Installer/MinGW%205.1.6/MinGW-5.1.6.exe and gdb-7.1-2-mingw32-bin.tar.gz http://freefr.dl.sourceforge.net/project/mingw/GNU%20Source-Level%20Debugger/GDB-7.1/gdb-7.1-2-mingw32-bin.tar.gz and MSYS-1.0.11.exe http://ovh.dl.sourceforge.net/project/mingw/MSYS%20Base%20System/msys-1.0.11/MSYS-1.0.11.exe Getting the newer MSYS versions is a pain since there is no single installer any more.
Marc, you just looked at this very help page with bug 306901. Maybe you could take a look at this request too?
(In reply to comment #1) > Marc, you just looked at this very help page with bug 306901. Maybe you could > take a look at this request too? The MinGW file list on SourceForge is being worked on. I will take a look once that's done. http://www.mingw.org/story/File_list_on_SourceForge
I'll be looking at this today. I'd like us to recommend using Wascana to get the MinGW packages. That way everyone is using the same version line up.
(In reply to comment #3) > I'll be looking at this today. I'd like us to recommend using Wascana to get > the MinGW packages. That way everyone is using the same version line up. > As an alternative, the MinGW site itself, http://www.mingw.org also has an > installer. The installer probably shouldn't be mentioned, it's deprecated and won't be updated. > The CDT will find that install if it is placed in the default C:\MinGW directory. While this works, this is the last place CDT looks for MinGW. I'm thinking there should be a small section "How CDT finds MinGW and Cygwin" somewhere in the documentation and "Before you begin" would link to it.
(In reply to comment #4) > (In reply to comment #3) > > I'll be looking at this today. I'd like us to recommend using Wascana to get > > the MinGW packages. That way everyone is using the same version line up. > > > As an alternative, the MinGW site itself, http://www.mingw.org also has an > installer. > > The installer probably shouldn't be mentioned, it's deprecated and won't be > updated. Except for the fact that they keep updating it. > > The CDT will find that install if it is placed in the default C:\MinGW directory. > > While this works, this is the last place CDT looks for MinGW. I'm thinking > there should be a small section "How CDT finds MinGW and Cygwin" somewhere in > the documentation and "Before you begin" would link to it. I am really trying to steer people to use Wascana. I thought that was pretty clear in the text. And, yeah, it's the last out of five which isn't that big of a deal. And the others are there to support the installers I already mentioned in the order they are used.
(In reply to comment #5) > (In reply to comment #4) > > (In reply to comment #3) > > > I'll be looking at this today. I'd like us to recommend using Wascana to get > > > the MinGW packages. That way everyone is using the same version line up. > > > > > As an alternative, the MinGW site itself, http://www.mingw.org also has an > installer. > > > > The installer probably shouldn't be mentioned, it's deprecated and won't be > > updated. > > Except for the fact that they keep updating it. Except for the fact that "Note: The automated installer is now considered deprecated, and is currently unmaintained; it will not install GCC 4. You will get GCC 3 using this method. If you want to install the latest GCC release, use the Manual Installation method below." and mingw-get is in alpha. ;) I would've preferred a link to http://www.mingw.org/wiki/Getting_Started and no mention of the installer. (In reply to comment #5) > I am really trying to steer people to use Wascana. I thought that was pretty > clear in the text. And, yeah, it's the last out of five which isn't that big of > a deal. And the others are there to support the installers I already mentioned > in the order they are used. Looking for MinGW in PATH is useful. I find it weird that this is not documented. Anyway this is all pretty minor so you can probably mark this as resolved.
(In reply to comment #4) > I'm thinking there > should be a small section "How CDT finds MinGW and Cygwin" somewhere in the > documentation and "Before you begin" would link to it. I think this section would be something useful in itself. There is much confusion among the users about how CDT finds these toolchains and why it doesn't.
(In reply to comment #6) > (In reply to comment #5) > > (In reply to comment #4) > > > (In reply to comment #3) > > > > I'll be looking at this today. I'd like us to recommend using Wascana to get > > > > the MinGW packages. That way everyone is using the same version line up. > > > > > > > As an alternative, the MinGW site itself, http://www.mingw.org also has an > installer. > > > > > > The installer probably shouldn't be mentioned, it's deprecated and won't be > > > updated. > > > > Except for the fact that they keep updating it. > > Except for the fact that > > "Note: The automated installer is now considered deprecated, and is currently > unmaintained; it will not install GCC 4. You will get GCC 3 using this method. > If you want to install the latest GCC release, use the Manual Installation > method below." At any rate mingw.org is a mess and gcc 4 isn't really official there. That's why I get it from tdragon.net for Wascana. And I notice other projects recommending getting gcc 4 from there. If I do anything, it would be to remove references to mingw.org all together ;)
(In reply to comment #7) > (In reply to comment #4) > > I'm thinking there > > should be a small section "How CDT finds MinGW and Cygwin" somewhere in the > > documentation and "Before you begin" would link to it. > I think this section would be something useful in itself. There is much > confusion among the users about how CDT finds these toolchains and why it > doesn't. It's up to the toolchain integration to write code to find the toolchain. As far as I know, only the MinGW and Cygwin toolchains do that in the CDT itself. The others rely on the toolchain being in the path. I wrote the MinGW to only support Wascana and the default C:\MinGW location, and will only support Wascana going forward. And I do not support Cygwin with CDT and personally recommend against it. Someone else can take care of that. At any rate, marking fixed as I think it's clear enough for users to figure out what to do.
