User Activity

  • Posted a comment on discussion Open Discussion on MinGW-w64 - for 32 and 64 bit Windows

    Nobody's stopping you :). Thing is, Windows-directed interest in GCC is minimal at best, I'm surprised at this point it still even works. On the LLVM/Clang side, there was interest from, well, almost all big parties, including GPU vendors, to get the thing working well and cooperating with the rest of the Windows ecosystem. Microsoft themselves contributed some bits and pieces to the Windows codegen, and even ship Clang in their Visual Studio installers as an optional component. It always comes down...

  • Posted a comment on discussion Open Discussion on MinGW-w64 - for 32 and 64 bit Windows

    Clang manages this quite well though, supporting at least three different ABIs (Mac, MSVC, MinGW, Linux, ...) in one compiler. Also the Intel compiler used to implement the MSVC ABI details as well. So the idea isn't far-fetched. It's more that GCC doesn't have this feature (and probably never will).

  • Posted a comment on discussion Help on MinGW-w64 - for 32 and 64 bit Windows

    If it's a Unix makefile you may need to use "make" instead of "mingw32-make".

  • Posted a comment on discussion Help on MinGW-w64 - for 32 and 64 bit Windows

    C is a computer language. It doesn't "work" by itself. A compiler transforms code written in C to assembled machine instructions, which are more often than not, very specific to a single OS and CPU architecture. The assembled machine code is then linked to the C runtime environment which works on a specific OS, and sometimes even some compiler specific runtime code is needed to run the program. You can go out of your way to only link to OS libraries, but you will lose some features that C(++) provides....

  • Posted a comment on discussion Help on MinGW-w64 - for 32 and 64 bit Windows

    It won't fix the installer, but using MSYS2 to manage your MinGW-w64 installation is also an option: https://www.msys2.org/ It has various variants of the toolchain and a ton of prebuilt dependencies for you. Op di 15 feb. 2022 om 16:06 schreef Ravi saini ravi279@users.sourceforge.net: I faced this issue from 1 week please solve this issue MinGw Installer failure https://sourceforge.net/p/mingw-w64/discussion/723798/thread/5193c4891b/?limit=25#4cc9 Sent from sourceforge.net because you indicated...

  • Posted a comment on discussion Help on MinGW-w64 - for 32 and 64 bit Windows

    Yes, the 32-bit toolchain is as complete as the 64-bit one, and includes all the compiler support libraries. Note that if you use a system like MSYS2, you can easily install both, along with a huge list of 3rd party libraries that are prebuilt for you. You can find it here: https://www.msys2.org/ The x86_64 is a synonym for amd64 and x64. amd64 is the "original" name for the architecture, as AMD "invented" the 64-bit extensions for x86. x86_64 was introduced by Intel when their processors started...

  • Posted a comment on discussion Help on MinGW-w64 - for 32 and 64 bit Windows

    The problem is that your toolchain isn't set up for multilib compilation. There's no 32-bit libraries present. Your simplest option is to use a separate 32-bit toolchain to build for 32-bit.

  • Posted a comment on discussion Help on MinGW-w64 - for 32 and 64 bit Windows

    It is most definitely possible. There are two ways to accomplish this: 1. Link statically with the GCC runtime. The linker argument "-static" will tell GCC to link everything statically. This is a carpet bomb approach, and there are more fine-grained options if you need them. I suggest the second option though: 2. Distribute the GCC runtime DLLs together with your application (the dots stand for something that tends to be different depending on how GCC was built): - libgcc....dll: always required....

View All

Personal Data

Username:
rubenvb
Joined:
2009-10-31 15:05:19

Projects

This is a list of open source software projects that rubenvb is associated with: