On sexta-feira, 31 de agosto de 2012 16.05.14, Peter Kümmel wrote: > On 30.08.2012 18:16, Thiago Macieira wrote: > > My suggestion on how to proceed is to choose one that offers the following > > or> > > most of the following: > > - most recent GCC (4.7 preferably, 4.6 if not) > > - *working* GDB and tested with Creator, with Python support > > - large file support, threading > > - zero-overhead exceptions (no SJLJ exceptions) > > - standard win32 headers, if possible using the Platform SDK headers > > - large set of win32 import libraries > > - 32 and 64-bit in one package > > - make with -j support > > - if this exists: can link to .dll directly, instead of import libs > > - should be also available in common distros as cross-compiler
That's secondary, like the import libraries (they can be recreated) and make -
j support.
It needs to work on Windows, first and foremost. And if the one that we find to
work best doesn't have standard cross-compilation packages... well, no big
loss.
> So I would say mingw-w64 is the choice.
>
> And if the Windows mingw-w64 setup misses some features we
> should ask if this could be changed by the mingw-w64 project.
True, like zero-overhead exceptions, GCC 4.7 and a working GDB. Those are a
must.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
