2013/6/23 LRN <lrn1986@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 23.06.2013 17:15, Ruben Van Boxem wrote:
> Hi everyone,
>
> I have come to the conclusion that my MinGW-w64 builds bring too little to
> the table for me to continue maintaining them.
>
> I strongly encourage you to use the plethora of toolchains in a multitude
> of configurations available at mingw-builds. Comparing download numbers
> they have a much higher visibility, and e.g. their adoption by the Qt
> Project speaks of their quality. They have succeeded in doing what I missed
> when I decided to start building GCC, so my effort spent in doing that is
> now wasted.

Since you brought this up, i have a question: how did you make your
toolchains? And how are mingw-builds' toolchains made? Are they
cross-compiled from *nix, or are existing W32 toolchains used to
[cross-]compile them?

Mingw-builds toolchains are builded in windows or wine under MSYS.
As I know Ruben's toolchains are cross-compiled from Linux.
 
- --
O< ascii ribbon - stop html email! - www.asciiribbon.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)

iQEcBAEBAgAGBQJRxz8hAAoJEOs4Jb6SI2CwhroH+QHQaSATuB07H8T2BZrkvAM6
n7hHY2FUjvAEY7eVeHMiLEflXe6VCIgW063zYAi2XShHMEQHdb7IIj5A6FEzuEKZ
qGDAFEnsmKYa2CsvFxJvwGM1m+vNpcSq9JConmIFf/TiruEL1S5iPKANhpa9JbIb
16VcvJUbFUpH4CFpObWhvvpRSulgaIEifa5Pt5hTwfYLeDlHTU+9yEE/fLzMjh+y
5NY5j+WKTmFAK/dkEJebN2Q0Ko7MiBvYsSsVeUO7Rmmcbve+GTFaEi12VHFlK9ow
M41iy5pknGhhPLeqyNNL4/ZDHHNgTK9dMwgYIiRRywMrIYeb/chHrdai4ABfSss=
=/InE
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public