2012/5/11 MARTIN Pierre <[email protected]>: > Dear Ruben, dear list readers, > >> I suggest using a native MinGW-w64 toolchain to build Qt. Qt does not >> support cross-compiling (just look at the OpenSuse or Fedora mingw-w64 Qt >> package build scripts: they patch the hell out of Qt's build >> infrastructure). >> >> Ah! But i *am* using a native MinGW-w64 toolchain when using the automated >> build, no? > > No, that's an oddity of the automated builds that they're always built as a > cross-compiler for some reason unknown to me. You can tell by the absence of > a plain (unprefixed) gcc.exe. in the "bin" directory. > > Ah! i wasn't aware of this fact, and the later is a very good trick to know > wether the build is native or not, and this might have a "sticky" on the > MinGW general explanations. i will keep that in mind. > >> Also, note the eMail i have just sent to the list in answer to Kai, when >> using SeZero's MinGW build (For compiling to / from 32 bit on MSys), it >> seems to work. Why? > > This is a native build. > > i understand now. Thanks for explaining. > > Following what Ruben just told me, i have another question. i have just > discovered the TDM-GCC packaging. It is very sexy, as it offers pre-packaged > binary online / offline installers. > However: > - Whatever mirror is selected, the "Show Details" buttons is not active, > making the process opaque. But that's okay. > - When using the Europe -> France -> Free mirror, the package > make-3.82-mingw32-bin.tar.lzma cannot be found on the server (404 type > error). Is Dragon part of this list, or is it another project mailing list i > shall subscribe to to report the problems i encounter? Hmm, I heard that some people on MinGW.org reported about download failures with 404 error, but I assume it isn't related. If this is a sourceforge-mirror/link then you might want to address this issue to sourceforge directly. Or report it directly to the related project.
> - After installing from anonther mirror, i can see that in my installation > folder, only g++.exe exists, no "xxx-yyy-zzz-g++.exe" and friends exist, > only plain "g++.exe" and friends. Does Ruben's rule applies, and does that > mean that the toolchain i just have installed is native? > > A last question from my global confusion: what would be the recommended way > of getting this so called "native" toolchain? On Ruben's version? TDM's > version? SeZero's version? This is quite confusing :) Well, this we handle as a pretty private choice ;) The builds by Ruben will become - at least so it is planned - official releases of mingw-w64 for specific gcc-version. Ozkan's toolchain are well maintained, don't provide all new features/enhancements, but are known to be pretty robust. We co-operate with TDM and TDM's installer is for sure the simplest way to get mingw-w64 toolchain installed. I would go for Ruben's build, but this is just my private choice. Regards, Kai ------------------------------------------------------------------------------ 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
