(solved) more struggles with ESP-IDF, tool installation

[mzimmers]

Hi all -

I've been trying to get my build environment right for a few days now. In an attempt to start from scratch, I've deleted my existing IDF directory, my toolchain directory and anything else I could think of. When I try to install release/V4.0 using the Windows setup tool, I get this error at the end:

Code: Select all

---------------------------
Setup
---------------------------
Unable to execute file:

C:\Users\mzimmers.CYBERDATA\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\ESP-IDF\ESP-IDF Command Prompt (cmd.exe).lnk



ShellExecuteEx failed; code 2.

The system cannot find the file specified.
---------------------------
OK   
---------------------------

Any ideas? Thanks...

[WiFive]

Does the shortcut exist in your start menu?

[mzimmers]

Does the shortcut exist in your start menu?

No, it isn't. Shouldn't the setup program create it for me?

[mzimmers]

I think I found the cause of this problem -- the tools setup program prompts for "create desktop shortcut for ESP-IDF Tools Command Line." I interpreted this to literally mean a shortcut located on the desktop, and un-checked it. Evidently, though, this option controls the creation of the shortcut that goes into the pathname I posted above. Probably my fault for not better understanding Windows nomenclature.

I'm still not out of the woods yet, though. Now, when I invoke that shortcut, the terminal displays:

Code: Select all

Using Python in C:\Users\mzimmers.CYBERDATA\AppData\Local\Programs\Python\Python37\
Python 3.7.3
Using Git in C:\Program Files\Git\bin\
git version 2.21.0.windows.1
IDF version does not include export.bat. Using the fallback version.
IDF version does not include tools\tools.json. Using the fallback version.
IDF version does not include tools\idf_tools.py. Using the fallback version.

Setting IDF_PATH: C:\esp-idf

Adding ESP-IDF tools to PATH...
    C:\Users\mzimmers.CYBERDATA\.espressif\tools\xtensa-esp32-elf\1.22.0-80-g6c4433a5-5.2.0\xtensa-esp32-elf\bin

According to the docs, I should have export.bat, yes? More troubling: why is it adding the path to the 5.2 compiler -- isn't that for V3? I was expecting to see the 8.2 compiler. My application build fails, too.

[mzimmers]

Figured it out: when selecting the option to use a current IDF directory, it's the user's (my) responsibility to ensure that the directory contains a compatible version of the IDF. Mine was still set to v3.3; allowing the setup tool to install release/v4.0 cleared up the above problems.

Duh...