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.
--
Regard
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 googlin
