On Tue, 12 Jan 2021, Liu Hao wrote:
While we’re at it, how could we reflect the target CRT (MSVCRT, UCRT, or one
of the version-specific RTs)?
Ideally they should be denoted by distinct triplets. For example, on Linux
`*-*-linux` and
`*-*-linux-gnu` are triplets for Glibc, while targets
在 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
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-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
On 1/10/21 9:51 PM, Peng Yu wrote:
>>> They look like gcc and g++. But their options (according to --help)
>>> are much fewer than the gcc and g++. What are the options are missing
>>> in the *-w64-mingw32-* tools?
>> How are you testing this, and on what system?
> I use the --help option of
Hi Peng,
I've also noticed that some options for gcc are not listed in the output of
--help. I generally look here for help:
https://gcc.gnu.org/onlinedocs/gcc/Option-Summary.html
and then I just try the option I want and see if the compiler accepts it.
Some work, some don't. I have not found a
> > They look like gcc and g++. But their options (according to --help)
> > are much fewer than the gcc and g++. What are the options are missing
> > in the *-w64-mingw32-* tools?
> How are you testing this, and on what system?
I use the --help option of *--w64-mingw32-gcc on Mac OS X.
--
On 1/10/21 6:46 PM, Peng Yu wrote:
>> 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
> 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 wiki[0], or just by
On 10.01.2021 5:11, Peng Yu wrote:
I see the following files installed by `brew install mingw-w64`. I
don't quite understand what `i686-w64-mingw32` and
`x86_64-w64-mingw32` means. Could anybody let me know?
Welcome to the world of GNU. These are cpu-vendor-os triplets (yes, mingw32 is
not
Hi,
I see the following files installed by `brew install mingw-w64`. I
don't quite understand what `i686-w64-mingw32` and
`x86_64-w64-mingw32` means. Could anybody let me know?
If I want to compile windows binaries on Mac OS from the following .c
and .cpp files, could anybody let me know what
13 matches
Mail list logo
