在 2021/1/11 下午11:00, Stephen Kitt 写道:
> On Mon, 11 Jan 2021 22:07:42 +0800, Liu Hao wrote:
> [...]
>> There is no special meaning about `w64` itself. `mingw32` on the other hand
>> specifies the ABI, so all `i686-*-mingw32` targets are considered
>> ABI-compatible.
>
> Are they really though? It
> Hmmm why aren't those IDLs imported from Wine?
1. Huge confusion. IExtractIcon is in -- shlobj_core.h in WinSDK,
shlobjidl.idl in wine, shlobj.h in mingw-w64.
2. Files differ largely between mingw-w64 and wine.
___
Mingw-w64-public mailing list
On Mon, 11 Jan 2021 22:07:42 +0800, Liu Hao wrote:
[...]
> There is no special meaning about `w64` itself. `mingw32` on the other hand
> specifies the ABI, so all `i686-*-mingw32` targets are considered
> ABI-compatible.
Are they really though? It seems to me that the triplet has ended up
在 2021-01-11 22:43, LRN 写道:
On 11.01.2021 17:07, Liu Hao wrote:
You invoked `i686-w64-mingw32-gcc` on your machine (the 'host'), which produced
a.exe suitable for
Windows on i686 (the 'target'). `x86_64-w64-mingw32-gcc` is similar.
Actually, if you want to be pedantic, his machine is
On 11.01.2021 17:07, Liu Hao wrote:
在 2021-01-10 23:46, Peng Yu 写道:
I just want to know the basic of the compilation commands. I see these.
$ i686-w64-mingw32-gcc main.c
$ file a.exe
a.exe: PE32 executable (console) Intel 80386, for MS Windows
$ x86_64-w64-mingw32-gcc main.c
$ file a.exe
在 2021-01-08 13:26, Biswapriyo Nath 写道:
So, I came up with this bizarre idea. I copy only the IExtractIcon{A,
W} interfaces from Wine's shlobjidl.idl file and create a dummy
shobj.idl file in mingw-w64. Then I generate the header file and
replace the generated interface to our shlobj.h file
在 2021-01-10 23:46, Peng Yu 写道:
Welcome to the world of GNU. These are cpu-vendor-os triplets (yes, mingw32 is
not an OS, welcome to the club) that identify the toolchain. i686 is 32-bit,
x86_64 is 64-bit - that's all you need to now with regards to mingw. A bit more
info can be found on the
