[Development] Choosing a new MinGW for Qt 5

Pau Garcia i Quiles pgquiles at elpauer.org
Fri Aug 31 09:02:44 CEST 2012


Hi,

On Fri, Aug 31, 2012 at 3:34 AM, Yang Fan <missdeer at gmail.com> wrote:
> Currently, official MinGW project provides GCC 4.7, but it uses SJLJ
> exception mode when TDM/MinGW-w64/MinGW-build projects use Dwarf2 exception
> mode which is known as zero-overhead exception.

I forgot to say we now have SEH exception support, which is the best
solution. See this thread in mingw-w64

http://sourceforge.net/mailarchive/message.php?msg_id=29641656


> All those MinGW and forks contain mingw32-make.exe util which does have -j
> option, but in fact this option doesn't make the real parallel build. Maybe
> sh.exe is needed, but this shell util will pass the incompatible path string
> so that the build process will be interrupted.

Are you sure of that? I remember reading a thread in the mingw.org
mailing list in which Earnie Boyd explained MSYS did the path string
translation and in most cases it worked fine. Or are you talking about
the cases where it fails? (recursive spawns, overinterpretation of the
path string, etc)

-- 
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)



More information about the Development mailing list