Re: [Mingw-w64-public] naming convention of mingw-w64 and compile Windows binary on MacOS

2021-01-10 Thread Peng Yu
> > 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. -- Regard

Re: [Mingw-w64-public] naming convention of mingw-w64 and compile Windows binary on MacOS

2021-01-10 Thread 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 wiki[0], or just by googlin

[Mingw-w64-public] naming convention of mingw-w64 and compile Windows binary on MacOS

2021-01-09 Thread Peng Yu
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 com