Hi, I was using the "former" way and it works, thank you. I've created a cross qt-makespec that points the compiler, linker, etc. to x86_64-w64-mingw32-g++. This one then can be used with the -xplatform configure switch.
However, this is quite a qt item, the only caveat is that all the qt-tools are cross-built together for a x64 target. So if someone wants to use a x86 host (qt and the cross-mingw) toolset to cross-build a qt app for a x64 target the qt-toolset is built the wrong way. For example in this case a qmake for the x86 host is needed to create makefiles for the x64 target, not the x64 qmake as it was built (using the -xplatform -platform configure switches). Maybe i've not figured out something yet for the straight way, but it works for me copying the right toolset together. Thanks again, .. frank On Sat, Jun 2, 2012 at 9:13 AM, fueb<[email protected]> wrote: > Hi, thanks to Marc for the answer, that gave me the trick. Well, I got > the compiler working with my "Hello World" using the -b option and your > mentioned target-triplet (-v lists the target-options built in the toolset): > > 'g++ ?-b x86_64-w64-mingw32 -m64' did the job (without modifying the > installation, though). Just use the right compiler. From your PATH variable that you were setting, it looks like you are using the internal binaries, not the ones you should be using. If you extract a cross compiler toolchain to C:\xx, you'll have this: xx/bin xx/x86_64-w64-mingw32/bin In the former, you'll have binaries of the form: x86_64-w64-mingw32-gcc. In the latter, you'll just have gcc. So basically, the full path is: xx/bin/x86_64-w64-mingw32-gcc or xx/x86_64-w64-mingw32/gcc Use the former, not the latter. You won't have any more problems. > However, this list isn't for building Qt, someone might know how to pass > the compiler-flags to the configure.exe shipped with Qt Source (I mean > the qmake step, not the specs file)? No idea how to use qmake, but tell it that the compiler name is "x86_64-w64-mingw32-gcc" instead of "gcc", and put the C:\xx\bin directory in your PATH instead of the one you're using. It'll all just work. ------------------------------------------------------------------------------ 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
