Dne 10.8.2012 15:50, Ruben Van Boxem napsal(a):
2012/8/10 <[email protected] <mailto:[email protected]>>Hi Ruben, thanks for the work. Just one point annoys me a bit: The Windows packages targeting win32 and win64 respectively differ in prefixes of binutils, e.g.: mingw32/bin/windres.exe vs. mingw64/bin/x86_64-w64-mingw32-windres.exe. This complicates things for those who (like me) need/want to use multiple mingw-w64 packages side by side. It would be cool if the packages would be consistent.I understand, but GCC/binutils classifies a i686-hosted x86_64-targetting compiler as a "cross-compiler", so it puts the prefix there automatically. I'm not going to remove it, because this is handy for configure scripts (just pass --host=x86_64-w64-mingw32 and everything should work automagically).If you want a 64-bit targetting compiler without prefixes, download the x86_64...-win64 package, which is a native 64-bit to 64-bit compiler. It is best to use the full native compiler for everything, unless you have special requirements (like compiling 64-bit code on 32-bit Windows, or you need a 64-bit linker executable).
Well, actually I would like the opposite: to have the 32bit targetting package also have the prefixes. Either way, currently the package has some binaries prefixed (gcc) and some not (binutils), which is IMO the worst possible situation.
Morous
------------------------------------------------------------------------------ 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
