What is Reddit's opinion of MinGW-w64?

From 3.5 billion Reddit comments

Another problem is that they are only supporting the official MinGW (which is out of date more often than not), and not the other variants such as MinGW-w64. Fortunately, it seems that they are fixing this in the next version.

I guess you mean <http://mingw-w64.sourceforge.net/>?

It's definitely not doing a good job of providing you with a simple thing you can just download and install. Then again, mingw.org hasn't been doing too well at that for a long time, either.

Win 64 open source compiler. On the left side panel click on the "WIN64" button under releases to download. I haven't used the windows compilers - but it says it has a fortran compiler.

These are the GNU ports for windows - hope this helps!

Best advise: get a good book and stick to it. Don't use the Ulmann book and especially don't use Dev-C++. Try to avoid using an IDE while learning: compile, link and run from the command line. See here for a good Windows C++ compiler.

I have found MSYS Git Bash shell to be fairly nice to use on Windows.

http://msysgit.github.io/

As for getting the GCC compiler suite, I think the MinGW-w64 is currently the best bet.

http://mingw-w64.sourceforge.net/download.php (look for Mingw-builds Project)

As for Java-based languages, it should suffice that you have Oracle JDK (8.0) installed on your machine. Not quite sure if it automatically updates the PATH, so check that if you run into trouble.

After installing the tools, you may need to update your PATH to make all the tools available on the Bash shell.

This should allow you to use the bash scripts provided in the repository.

Edit: I almost forgot - Git on Windows might modify the line endings to include carriage return. If you get some errors about invalid commands, then check that your git config preserves the Unix-style linefeeds.

http://stackoverflow.com/questions/2517190/how-do-i-force-git-to-use-lf-instead-of-crlf-under-windows

No. I'm keeping an eye on mingw-w64, but they're still stuck on code-based SJLJ (setjmp-longjmp) exception handling, which is not efficient. Their FAQ entry indicates that they may be moving to table-based EH.

If you have TDM-gcc, then use the 64 bit compiler if you have issues. Though, whatever is compiled with the generic option (32 bit) should run fine on 64 bit. I'd check if you have the tdm-gcc installed (some of the exe's are labeled as mingw), as the issue you've described is a known issue with the main mingw project. Any executable for windows via this sourceforge page also have the same issue.

Check your TDM-gcc /bin, the 64 bit executables are named with the pattern:

x86_64-w64-mingw32-c++.exe x86_64-w64-mingw32-g++.exe x86_64-w64-mingw32-gcc.exe x86_64-w64-mingw32-gcc-4.9.2.exe etc...

edit: directly from the TDM-GCC website (linked above):

> - The TDM64 edition is able to run on 32-bit and 64-bit systems, because the compiler executables are all 32-bit.

> - You can't mix 32-bit object code and 64-bit object code, or you'll get linker errors. These usually look like "undefined reference to ...", or "architecture of input file ... is incompatible with ...".

> - You can't use a 32-bit version of GDB to debug a 64-bit program. This is why the version of GDB provided with the TDM64 edition is a 64-bit-only program.

Also, make sure you're using the TDM64 bundle (center button, main page)

1. VIM (an improvement upon VI) is available on Windows: http://www.vim.org/download.php#pc

2. The MingW toolchain makes the linux build environment available on Windows. This includes GCC, Make, autoconf etc: http://mingw-w64.sourceforge.net/

I'm going to second Code::Blocks, and add that you should supplement it with MinGW-w64, a sort of continuation of MinGW that has ported the newer versions of GCC over and has several different setups (32-bit, 64-bit, different thread models, different exception models, etc.) so you can somewhat customize your build as needed (or just use the sensible defaults, of course).

Intel give a 30 day free evaluation license which might be sufficient for you. Otherwise 64 bit windows is a bit tricky... you could try mingw-64 binaries from here http://mingw-w64.sourceforge.net/

Although if it is a standalone binary and doesn't use many GB of RAM, 32 bit gfortran should work fine on 64 bit windows.

Do you mean "-W" "-Wl" is not recognized.
also "--verbose" instead of "-verbose"
Then I get alot of output which I am going through tomorrow.

What confuses me though is, that on the fftw page it says:
" These DLLs were created by us, cross-compiled from GNU/Linux using MinGW; the 64-bit version is possible thanks to the mingw-w64 project. "

So I would expect it to work out of the box. Do you have the opportunity to maybe reproduce my problem?

MSYS2

Like CygWin, it's a "minimal" UNIX-like environment for Windows. The compiler suite is actually mingw-w64, which is a fork of gcc, just like the original mingw and was originally intended to replace it, however now they're just two semi-independent projects.

It has a variant of pacman (which is in Arch Linux) as package manager, mintty as console emulator, bash or zsh as shells, vim, emacs, git, mercurial etc. and a quite strong toolchain for developing and building software. Of course its packages can be used outside of that shell, because they are true Windows binaries, linked to its own dll, just like in CygWin, and of course you can incorporate existing Windows software in your workflow.

I think it's much better organized than CygWin or the environment around Git for Windows, not to speak of self-built environments around mingw.

Side note to prevent confusion: mingw* are compiler suites, msys and msys2 are tools that together build an evironment around this compiler, and msysgit is a distribution of the original msys with git sources, used to build git on a Win system. Git for Windows is an already built distribution of git, not the sources, but it's built from msysgit.