Win10 Eclipse Build Failures with eclipse_make.py (GIT8266O-700)

[Doubletop12]

Environment

• Development Kit:

• IDF version (git rev-parse --short HEAD to get the commit id.): $ git rev-parse --short HEAD d11de779

• Development Env: [Eclipse]

• Operating System: [Windows]

• Power Supply: [USB]

Build in Eclipse results in

**Error: Program "python C:\msys32\home\Pete\esp\ESP8266_RTOS_SDK\tools\windows\eclipse_make.py" not found in PATH**
PATH=[C:\msys32\mingw32\bin;C:msys32\usr\bin;c:\Windows\System32;c:\Windows;c:\Windows\System32\Wbem;c:\Windows\System32\WindowsPowerShell\v1.0\;C:msys32\opt\xtensa-esp32-elf\bin;C:msys32\usr\bin\site_perl;C:msys32\usr\bin\vendor_perl;C:msys32\usr\bin\core_perl;C:msys32\opt\xtensa-lx106-elf\bin]

No end of juggling with the forward and back slashes resolved the problem

Hard wiring the build command

C:/msys32/mingw32/bin/python C:/msys32/home/Pete/esp/ESP8266_RTOS_SDK/tools/windows/eclipse_make.py

didn't work either, however the same command in mingw32 console works fine . Again any combination of forwards or back slashes and /c/ or C:\ didn't work either.

Hardwiring the make command made more progress although reports of cygwin errors.

[johnhaire89]

I had the same issue and just got it working. https://github.com/espressif/esp-idf/issues/1580#issuecomment-896719308

In the C/C++ Build settings, set "Build command" to be just "python"

Then go to the "Behavior" tab, select "Use custom build arguments". In the "Build arguments" box, put "${IDF_PATH}/tools/windows/eclipse_make.py"

I'm not sure exactly what's going on or if my fix is the optimal one (it prevents me from adding on any standard build arguments), but eclipse seems to be interpreting python ${IDF_PATH}/tools/windows/eclipse_make.py as one big command, rather than a command and an argument.

[xuanvuong1702]

I facing with same error, pls help