> 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 googling.
What does "w64" mean? What does w32 in mingw32 mean? > If you are _this_ inexperienced, consider using a build system. Meson[1] and > CMake[2] are all the rage for C/C++ these days. A buildsystem will invoke the > toolchain for you, no need to muck around with command lines. 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 a.exe: PE32+ executable (console) x86-64, for MS Windows 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? Also, the resulted a.exe is considered as virus file and deleted immediately in the following VM. Why is it so? https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/ -- Regards, Peng _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
