Caution - Removing materials from your path may compromise your system!
Interestingly, you need to not only add the MinGW bit to your path, but you also need to make sure that some things are not in your path *. In my case, I saved the entire path variable as a backup, removing all non-system ones from my path except MinGW and CMake, leaving:
C:\MinGW\bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files (x86)\CMake\bin
You must use the appropriate elements in your system path.
At first I tried to do this with a batch job that launched CMake, but it looks like the CMake GUI was returning and grabbing the System Path variable instead of the "Path" command line, which I typed and confirmed as above before running CMake.
By the way, I made a backup of the entire Windows virtual machine before starting!
* For example: various links, including known problems , specify sh.exe. I inherited this virtual machine from my client and hacked it further, so it’s easier for me to use the clean path for my cross-compilation task and come back after that ...
sage Apr 12 '16 at 16:58 2016-04-12 16:58
source share