Hello,
2010/7/29 NightStrike <[email protected]>:
> On Thu, Jul 29, 2010 at 11:04 AM, Earnie <[email protected]> wrote:
>> Luis Lavena wrote:
>>> On Wed, Jul 28, 2010 at 1:54 PM, Earnie
>>> <[email protected]> wrote:
>>> The suggested target triplet for 64bits is x86_64-pc-mingw32
>>>
>>> Notice the "pc" part, which indicates vendor "pc" (mingw.org) vs.
>>> w64 (mingw-w64 project).
>>>
>>
>> Yes, as I said misinformation abounds.
>
> We switched to using the vendor part of the triplet after that
> document was written.
>
> The vendor portion is now very important to distinguish what we do
> here from what mingw.org does. I agree that the choice of moniker
> blows, but it is what it is.
To clarify this point about vendor-key -pc- and -w64-. It is more a
technical need then a really wish what brought me to introduce it. The
mingw-w64 provide a so called *compatible* mode by specifiying the
vendor-key as -pc-, but this leads also to the lack of some additional
features we provide. For example multilib support, unicode-startup,
cross-compiler acts like native (comes up in 4.6), etc.
>>> I undestand that 64, w64 and mingw32 all in one sentence can confuse
>>> users (indeed it confuses me), but I believe is less confusing than
>>> running:
>>
>> The original project is MinGW, no 32. It was named such so that when 64
>> bit Windows was developed it would create *-*-mingw64 to imply a 64 bit
>> Windows ABI. The *-*-mingw32 is meant only to imply 32 bit Windows ABI
>> as provided by the MinGW project.
>
> mingw64 is inappropriate, as Win64 and Win32 are too closely
> intertwined. This is not like Win16 vs Win32. There's a lot of
> information readily available on why we chose to not make it mingw64
> instead of mingw32.
Indeed, x64 and x86 (or i?86) are already the architectures. The
appended 32 on mingw is pretty superflous.
> That said, I agree that just plain "mingw" is better. Although
> really, it should even be simplified to just plain "windows". As in,
> x86_64-w64-windows. But that's a perfect world where all bike sheds
> are blue (I like blue).
>
>>>
>>> sh -c "./config.guess"
>>>
>>> and getting the completely wrong platform.
>>>
>>> If supplying MSYSTEM=MINGW32-W64 can target i686-w64-mingw32 and
>>> MSYS=MINGW64 can target x86_x64-w64-mingw32, I believe one less
>>> error-prone and WTF moment could been eliminated.
>>>
>>
>> This is just wrong. *-*-mingw32 implies a target of 32 bit Windows ABI
>> so MSYSTEM=MINGW32-W64 is meaningless. I also think it is wrong to
>> introduce i686-w64-mingw32 as a triplet, it should remain
>> i686-pc-mingw32 regardless of which project is producing the binaries.
See above why this isn't correct.
Kai
--
| (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination
------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
