3 ms·

There's something abhorrent about running gcc on windows.

• 2h 3y ago
  Might want to tell that to the Rust programming language, Go, Zig and many others. You think Windows dev shouldn't happen just because you don't like it?
  • dlivingston 3y ago
    They all use the LLVM backend -- nothing to do with gcc. AFAIK there is no native GCC compiler for Windows. You have to use a pseudo-Linux environment like Cygwin or MinGW.
    • 2h 3y ago
      > AFAIK there is no native GCC compiler for Windows might want to check your facts before spouting nonsense. there is, and has been for many, many years. more than one in fact: https://github.com/mstorsjo/llvm-mingw https://github.com/mstorsjo/llvm-mingw https://packages.msys2.org/base/mingw-w64-gcc https://packages.msys2.org/base/mingw-w64-gcc https://mirrors.kernel.org/sourceware/cygwin/x86_64/release/mingw64-x86_64-gcc https://mirrors.kernel.org/sourceware/cygwin/x86_64/release/...
      • dlivingston 3y ago
        ??? Those are MinGW LLVM/Clang, MinGW GCC, and Cygwin GCC, respectively. I don't count either as truly native Windows, like I said earlier -- Cygwin certainly isn't.
        • 2h 3y ago
          You are really showing your ignorance. Any cygwin packages marked mingw64 do not rely on the cygwin DLL for build time or run time.
• smoldesu 3y ago
  It's honestly more "abhorrent" running them on Mac. GNU's Not Unix, Windows is not UNIX, but macOS 10+ is.
  • opless 3y ago
    It's indeed a good job, that the default compiler is clang then ;-)