Thread: Command Line g++ Issues

I'm trying to compile a simple program with g++ from the command line. When I checked my laptop's PATH I see that it already includes a compiler from the Dev-C++ download: C:\Program Files (x86)\Dev-Cpp\MinGW64\bin and so I did not install anything else and tried both:

F:\demo>g++ demo2.cpp

AND

F:\demo\g++ -o demo2 demo2.cpp

and in both cases I get the error message:

g++: error: CreateProcess: No such file or directory

though when I run F:\>cd demo I can see the demo2.cpp file listed in this folder

I am wondering if the g++ from the Dev-C++ download is the issue here and if I need to remove this from the PATH and download the compiler separately and add it to the PATH. Any help, as ever, much appreciated. Thanks

Does plain g++ --version work? I think the spaces in Program Files (x86) might be tripping it up.

I would suggest to place compiler toolchains (and libraries you build) into a path without spaces, e.g. C:\dev\MinGw64. That's not quite in line with Windows' standard location for binary files, but imo the best solution to save yourself headaches later on.

Since someone else also asked a GCC related question today, I'll just repeat myself and recommend mingw-w64 builds, e.g. this collection. I never had any issues with those and they support std::thread on Windows, which is nice.

Are there other Windows C++ compilers that don't support std::thread? Oh... Oh god...

That's what I remember being an issue dealing with GCC based toolchains on Windows, but maybe it's a non-issue now. Something about winpthreads, licensing issues, etc. where users stuck to the Windows API for thread management instead of the "new" C++11 features.

@Guest: Thank you for the suggestion, the mingw-w64 builds work perfectly. In fact, even the CodeBlocks\MinGw\bin works fine, it seems to be a Dev-cpp issue in my case. Cheers,