[Windows] 'g++' could not be spawned about atom-gpp-compiler

[kriscross07]

Open command prompt and enter g++ --version and paste the output.

[toadicus]

>g++ --version
g++ (GCC) 4.9.3
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

[kriscross07]

In Atom, press Ctrl + Alt + i (I think it's that in Windows, it's Ctrl + Shift + i on Linux) and click on the Console tab, and paste require("child_process").spawn("g++", ["--version"]).stdout.on("data", (data) => {console.log(data.toString());});, then enter require("child_process").exec("g++ --version").stdout.on("data", (data) => {console.log(data.toString());});.
What do those output?

[toadicus]

require("child_process").spawn("g++", ["--version"]).stdout.on("data", (data) => { console.log(data.toString());});
Socket {_connecting: false, _hadError: false, _handle: Pipe, _parent: null, _host: null…}
events.js:141 Uncaught Error: spawn g++ ENOENTexports._errnoException @ util.js:856ChildProcess._handle.onexit @ internal/child_process.js:178onErrorNT @ internal/child_process.js:344doNTCallback2 @ node.js:465_tickCallback @ node.js:379
require("child_process").exec("g++ --version").stdout.on("data", (data) => {console.log(data.toString());});
Socket {_connecting: false, _hadError: false, _handle: Pipe, _parent: null, _host: null…}

[kriscross07]

This seems like an issue with Node.js. What happens if you move C:\MinGW\bin to the beginning of %PATH%?

[toadicus]

Moving the path to the beginning had no effect. Though, I had to do that from the command line (Windows' normal tools don't let you do that) and I don't actually know if that applied to the atom process when I ran it. I did launch it from the same command window, but who knows.

[toadicus]

So, I think I may have found the issue, but I'm perplexed as to how to resolve it. In the atom console, I printed the path and got this:

> process.env.PATH
< "C:\Python35;;/usr/local/bin;/usr/bin;/bin;/usr/sbin;/sbin"

[toadicus]

I may have resolved the issue by completely uninstalling atom, deleting all of its leftovers, and reinstalling. Closing this for now; thanks for the support!