Re: [Mingw-users] Stop on first error?

[Peter R. <p.r...@sh...>]

> So, you think it necessary to provide a GUI installer for a product which
> is designated for CLI use?  If a user can't type (at a CLI prompt):
>
>     mingw-get install foo
>
> how do you expect them to manage:
>
>     gcc -o foo.exe foo.c
>
> (or the more complex sequence of commands typical of a real project)?

1) I can honestly say in many years of using various C(++) compilers, I 
have never once invoked a compiler from the CLI! (Apart from indirectly 
via make files.)  I have only ever used an IDE for my own projects. 
Everybody I know uses an IDE. I suppose there must be command-line 
warriors left but they're surely a dying breed.

2) Typing mingw-get install foo once isn't the problem. It's the fact 
that you have to type mingw-get install umpteen times (for gmp, mpfr, 
mpi, etc.) to get the toolchain working. If you want ada or fortran 
there's other stuff to type. Of course this could all be usefully 
automated in batch files, one for the base C compiler, one for C++, 
another for C and fortran, etc., etc.  That gives a 1-from-N choice 
where N is a large number. A GUI is an obvious way to solve that 
1-from-N problem...