I think it's a problem that the most popular platform is the "hardest"
to setup and as you say, my concern is with the 500 000 downloads,
which a majority are probably on Windows. Doug, I like what you are
doing with Wascana and I'll definitely keep an eye on it. That said,
I'd really like to see the MinGW/MSYS installation itself improved and
there is not much that can be done on the CDT side. One of the big
problem is the MinGW automated installer; it is not planed to be
supported anymore (no gcc 4) and doesn't provide a good make and gdb is
not included. There is mingw-get but I'm not sure how and when this
will work. I think it would make sense to invest some time helping
MinGW but I guess some of you would have a hard time justifying that to
your bosses.
Marc-Andre
On 10-03-02 3:50 PM, Doug Schaefer wrote:
To clear up what we have today, when creating a managed
project using MinGW, it actually uses the internal builder, no make
required.
If
you are creating a Makefile project, then you do need make. The MinGW
gang don't recommend using the mingw-make, which makes me wonder why
the provide it. They'd prefer you use MSYS which provides a small shell
environment.
The
CDT has a built-in search path to find MinGW, but I don't think I put
one to find MSYS. I'll probably fix that up in preparation of a new
version of Wascana for CDT 7. With Wascana, the mingw and msys
directories appear in the eclipse directory next to plugins and
features.
BTW,
I always recommend MinGW over Cygwin. Cygwin requires linking with
their GPL cygwin1.dll, which makes everything you build with it GPL (or
with exception any other OSI approved license), which is fine if that's
what you want. And in the past we've had a lot of trouble with the way
it hides the underlying Windows native, especially since the CDT is a
native application. But anyway, there's always been debate about that.
Doug.
On Tue, Mar 2, 2010 at 3:00 PM, John Cortell
<rat042@xxxxxxxxxxxxx>
wrote:
Thanks, Ed. Installing MSYS (and adding it to my PATH) fixed
both issues.
That is some very helpful documentation. Not something I would have
expected.
John
At 01:43 PM 3/2/2010, Ed.Swartz@xxxxxxxxx
wrote:
Content-Language: en-US
Content-Type: multipart/alternative;
boundary="_000_F69D6574A9EB154AB7DEA2BC80F07DDF22E273FF47NOKEUMSG03mgd_"
Hi John,
I went through this a few weeks
ago.
Actually the help is your friend in this case. It tells you exactly
which packages you need to install and *where* (i.e. c:\mingw, which is
probably your issue).
C/C++ Development User Guide >
Before You
Begin
But I agree, there should at least
be an
error explaining why the tool-chain is unsupported, and better yet, an
obvious way to reconfigure the path.
-- Ed
- From: John Cortell
[
mailto:rat042@xxxxxxxxxxxxx]
- Sent: Tuesday, March 02, 2010
1:25 PM
- To: cdt-dev@xxxxxxxxxxx
- Subject: [cdt-dev] builder and MinGW
- I'm trying to use CDT with MinGW for the first time and am
having
some trouble. I wonder if I'm doing something wrong or this is just
indicative of a bad out-of-the box experience for our MinGW users. The
problems I'm experiencing are with a C project I created using the
wizard, having chosen MinGW as the toolchain.
- For starters, mingw's make is called mingw32-make. When I
build the
project, the builder assumes 'make' is available. So, I hit that wall
right out of the gate. I can get passed this by renaming the mingw make
program to 'make'. Are we expecting users to take this manual step?
- Now the project builds but I get these warnings in the
console
- **** WARNING: The "Debug" Configuration may not
build ****
- **** because it uses the "Cygwin GCC" ****
- **** tool-chain that is unsupported on this system.
****
- The used tools (as showing in the Tool Chain Editor
properties page)
are:
- GCC Assembler
- GCC Archiver
- GCC C++ Compiler
- GCC C Compiler
- MinGW C Linker
- MinGW C++ Linker
- Note that I have not tweaked the wizard generated project.
Also, I
get the same behavior whether I use Gnu Make Builder or CDT Internal
Builder.
- Can someone enlighten me as to what I'm doing wrong or why
our MinGW
support is quirky?
- John
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
|
