mingw-w64

问题 Libraries built with Mingw-w64 require those dll: libwinpthread-1.dll libstdc++-6.dll libgcc_s_seh-1.dll I wonder what's up with that, what each dll does? Especially libgcc_s_seh, is that structured exception handling? I thought mingw couldn't work with seh. Why mingw requires to always bring those dll with your exe? I wonder if I'm just wasting my time by not just using visual studio as a windows compiler. It's so bloated though, 9 gb for installation. 回答1: Especially libgcc_s_seh, is that

问题 I'm on Windows 10 and using the latest version of MSYS2 (with gcc installed: pacman -S gcc ) I'm trying to compile mingw-w64-headers and mingw-w64-crt from mingw-w64-v7.0.0 Inside of my MSYS2 installation directory C:\msys2 I have created the folder mingw-w64 which I reference in the prefix argument below. To compile each of these I use the same steps (replace name of library where appropriate): mkdir mingw-w64-crt && cd mingw-w64-crt ../mingw-w64-v7.0.0/mingw-w64-crt/configure --prefix=

问题 I'm on Windows 10 and using the latest version of MSYS2 (with gcc installed: pacman -S gcc ) I'm trying to compile mingw-w64-headers and mingw-w64-crt from mingw-w64-v7.0.0 Inside of my MSYS2 installation directory C:\msys2 I have created the folder mingw-w64 which I reference in the prefix argument below. To compile each of these I use the same steps (replace name of library where appropriate): mkdir mingw-w64-crt && cd mingw-w64-crt ../mingw-w64-v7.0.0/mingw-w64-crt/configure --prefix=

问题 I'm on Windows 10 and using the latest version of MSYS2 (with gcc installed: pacman -S gcc ) I'm trying to compile mingw-w64-headers and mingw-w64-crt from mingw-w64-v7.0.0 Inside of my MSYS2 installation directory C:\msys2 I have created the folder mingw-w64 which I reference in the prefix argument below. To compile each of these I use the same steps (replace name of library where appropriate): mkdir mingw-w64-crt && cd mingw-w64-crt ../mingw-w64-v7.0.0/mingw-w64-crt/configure --prefix=

问题 I want to use the GDB debugger provided with the 64-bit version of MinGW-w64 (x86_64-w64-mingw32) to debug 32-bit targets created using the 32-bit version of MinGW-w64 (x86_64-w64-mingw32). According to Debug 32 bit application with gdb in 64 bit environment , this is entirely possible. I want to do this as it simplifies my setup. However, I am getting the following error messages from the debug console of VS Code: A bunch of "i386:x86-64 is not compatible with target architecture i386": 1:

问题 I want to use the GDB debugger provided with the 64-bit version of MinGW-w64 (x86_64-w64-mingw32) to debug 32-bit targets created using the 32-bit version of MinGW-w64 (x86_64-w64-mingw32). According to Debug 32 bit application with gdb in 64 bit environment , this is entirely possible. I want to do this as it simplifies my setup. However, I am getting the following error messages from the debug console of VS Code: A bunch of "i386:x86-64 is not compatible with target architecture i386": 1:

问题 I wanted to try out the new filesystem library in C++17, so tried copying the std::filesystem::current_path example from cppreference.com and compiling it using the latest version (16.0) of the MinGW distribution from nuwen.net on my Windows 10 x64 machine. This includes gcc v8.1 which should support the filesystem library according to cppreference.com compiler support page. Here is the code that I am trying to compile: #include <iostream> #include <filesystem> namespace fs = std::filesystem;

问题 I wanted to try out the new filesystem library in C++17, so tried copying the std::filesystem::current_path example from cppreference.com and compiling it using the latest version (16.0) of the MinGW distribution from nuwen.net on my Windows 10 x64 machine. This includes gcc v8.1 which should support the filesystem library according to cppreference.com compiler support page. Here is the code that I am trying to compile: #include <iostream> #include <filesystem> namespace fs = std::filesystem;

问题 I am top-posting EDITs so the reader does not need to locate the current status. This is a specific question related to the two python installations mentioned in Msys2: Maintaining two python installations $ pacman -Sl | grep "python " | grep "installed" mingw64 mingw-w64-x86_64-python 3.8.2-2 [installed] msys python 3.8.2-1 [installed] EDIT #2 : It became clear that readline s quoted below were not python packages, but for shells. As for readline for python, the files provided by each

问题 2 days ago, I was excited to note that MinGW-w64 released its gcc 8.1.0, revision 0. Unfortunately, a simple program #include <filesystem> int main() {} does not compile. It results in a bunch of errors inside <filesystem> , starting with C:/MinGW/mingw32/lib/gcc/i686-w64-mingw32/8.1.0/include/c++/bits/fs_path.h: In member function 'std::filesystem::__cxx11::path& std::filesystem::__cxx11::path::operator/=(const std::filesystem::__cxx11::path&)': C:/MinGW/mingw32/lib/gcc/i686-w64-mingw32/8.1