Hi NightStrike! Please let me clarify my comments, below.
On Mon, Sep 24, 2012 at 2:02 PM, NightStrike <[email protected]> wrote: > On Tue, Sep 11, 2012 at 10:51 AM, K. Frank <[email protected]> wrote: >> Hello Kai (and Qt Folks)! >> >> On Tue, Sep 11, 2012 at 10:55 AM, <[email protected]> wrote: >>>> -----Original Message----- >>>> From: ext Loaden [mailto:[email protected]] >>>> ... >>> There's nothing wrong with cross-compilation. But what we need first and >>> foremost is a reliable, native MinGW environment for developing Qt >>> applications, since the vast majority of Qt developers that develop for >>> Windows also develop _on_ Windows. Now one can argue that Qt itself could >>> still be compiled using a cross-compiler. But if we're not able to compile >>> Qt ourselves with the native toolchain, how can we be sure other complex >>> apps will work? >>> >>> I haven't found a stock native MinGW 64 bit package yet that can compile Qt >>> 5 + Qt Creator. Peter seems willing to experiment with a custom package, >>> but I personally do not see this for 5.0 . >>> >>> I think for 5.0 , we should therefore only put MinGW 32 bit gcc 4.7 as Tier >>> 2 or (preferably) Tier 1 platform. Support for MinGW 64 bit would be on a >>> best effort basis (Tier 3). >>> >>> Now for 5.1 (that is, earliest May 2013) we should definitely reevaluate >>> MinGW 64 bit as Tier 1 or Tier 2. >>> >>> What do you all think? I certainly don't want to discourage any effort in >>> getting MinGW-64 bit and Qt 5 to work, but rather want to be realistic in >>> what we should aim for with 5.0. [My previous comments start here.] >> Just my personal opinion: >> >> As much as I like mingw-w64, I think, as a practical matter, if >> working to get Qt 5.0 to build nicely with mingw-w64 would delay >> Qt 5.0 by a significant amount, then I would skip it. Better to >> move forward with Qt 5.0, and hope to get mingw-w64 support >> for Qt 5.1. > > What exactly does not work? Can you build a 32-bit Qt using a > mingw-w64 32-bit toolchain? To the extent that you are replying to me rather than to the thread in general or to Loaden's specific comments: For me, everything works fine (except for the minor issue of gdb slowness that Ruben thinks he's solved), so I can't give you anything that doesn't work. I should emphasize, however, that I have not tried to build any version of Qt 5, so I can't comment on any possible issues there. I did say that I felt it would be better to move forward with Qt 5.0 without mingw-w64 than to significantly delay Qt 5.0. But, I should clarify that I have no reason to think that getting Qt 5.0 to work with mingw-w64 would delay Qt 5.0. > You have our full support to get whatever's broken to work. My experience is that you and the others working on on mingw-w64 have been very responsive about addressing issues, so I am optimistic than any Qt 5.0 / mingw-w64 issues will be resolved promptly. I hope that my comments weren't read as implying anything to the contrary. Just to clear up any possible misunderstanding ... Anyway, thanks, as always, to the mingw-w64 team (and the Qt team too, of course)! Best. 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
