Re: mingw-targeted cross-compiler question

[Andy Koppe <andy dot koppe at gmail dot com>]

On 22 December 2010 15:12, NightStrike wrote:
> 2010/12/22 FrÃdÃric Bron:
>>>>> I checked the Make file, it used this flag:
>>>>> gcc -mno-cygwin -g -Wl,--add-stdcall-alias -Wl,--export-all-symbols ...
>>>>
>>>> replace gcc by gcc-3
>>>> gcc 4 is now the default on cygwin but the cross compiler is not
>>>> supported for that version.
>>>> FrÃdÃric
>>>
>>> What do you mean by not supported? ÂJonY maintains the cross compilers....
>>
>> I meant that i686-w64-mingw32-gcc exists but not i686-w32-mingw32-gcc.
>> I thought that w64 meant "built on win64" and mingw32 "run binary on win32".
>> So it seems to me that with cygwin running on a 32 bit windows, it is
>> not possible to cross compile to win32. However with a 64 bit windows
>> you can produce win32 applications.
>> However, I just tried to use i686-w64-mingw32-g++ on my win32 machine
>> with a hello world program and it produces an binary that can be used
>> from windows on that win32 machine.
>> So my question to the list: what is the meaning of w64 in the name?
>
> Basically, "stuff from mingw-w64.sf.net"
>
> The middle piece of the triplet is the vendor tag. ÂWe at mingw-w64
> are the vendors. ÂWe support win32 and win64, for both host and
> target. ÂI admit it's confusing, but we didn't come up with a better
> name fast enough.

Also, the 'mingw32' in the OS part of the triplet is hystorical
ballast. The '32' in there doesn't mean anything (anymore), and a
better name would have been plain 'mingw' or even just 'windows'.
Alas, compatibility concerns have stopped any change.

Andy

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple