Ruben Van Boxem wrote: > > This probably is mentioned somewhere on the wiki, but heck, here > goes: The "x86_64-w64-mingw32" and "i686-w64-mingw32" are target > triplets: - The first part is the archtecture: x86_64 (64-bit) and > i686 (32-bit) - w64 is the "vendor" part, usually it's pc, unknown, > gnu, etc... - mingw32 is the OS part. The 32 is somewhat confusing, > but derived from Win32, the API that all desktop Windows versions > adhere to and use. It has nothing to do with architecture. >
But I have i586 PC what do I do? (sarcastic remark, see below) > There were movements to rename mingw32 to mingw, but that never > happened for some strange unknown-to-the-world reason. > I forget reasoning here. I was the champion of the movement but decisions to leave it mingw32 because of history were the deciding compromise. > MinGW.org (the "mingw32" as you and pretty much the rest of the > cross-compiling world call it) misused its "monopoly" before > MinGW-w64 and was lazy, reducing the triplet to a single string: > mingw32, or if they were a bit nicer, i?86-mingw32. > Well actually we agreed to --host=mingw32 --target=mingw32 because i386 made no sense to someone using i686 and so to eliminate the confusion of the architecture part of the triplet we made our decision. It had nothing to do with being lazy, the original distributions had the triplet in full. > Hope this clears up the confusion. > Ditto. -- Earnie -- https://sites.google.com/site/earnieboyd/ ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
