Hello Paul! On Fri, Aug 31, 2012 at 9:28 AM, Pau Garcia i Quiles <[email protected]> wrote: > Hi, > > Qt Project is again trying to decide on what gcc to use on Windows. If > someone could drop by [email protected] and give more insight > (like: SEH vs Dwarf2 builds, std::thread, make -j support, etc), it'd > be great.
I would like to see something like 4.7.1 / 4.7.0 to get support for as much of the new c++11 standard as we can, including std::thread. My personal preference would be to go for 64 bits, although lowest common denominator would argue for sticking to 32 bits. There is a memory-exhausted issue with building recent versions of Qt with recent versions of mingw-w64. I don't know whose "fault" it is -- my guess is that there is an inefficiency in mingw-w64 that is triggered by the large size of Qt. I've been able to work around it, but it is a nuisance. Also, I've had a problem with recent versions of mingw-w64 gdb. It's slow as molasses loading up and/or initializing an application (minutes), but once the application starts, it seems to be fine. (I don't think that this is Qt specific.) Obviously, you need a stable enough and good enough version of gcc to get Qt built, but in general my preference would be for you to push up close to the mingw-w64 bleeding edge. Getting Qt built is a good test for the compiler, so you'd be helping the mingw-w64 project. Thanks for everyone's work on these tools. K. Frank ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
