Standard Setup of Toolchain for Windows¶
Currently only 64-bit versions of Windows are supported. 32-bit Windows can use the Legacy GNU Make Build System.
ESP-IDF requires some prerequisite tools to be installed so you can build firmware for supported chips. The prerequisite tools include Python, Git, cross-compilers, CMake and Ninja build tools.
For this Getting Started we’re going to use the Command Prompt, but after ESP-IDF is installed you can use Eclipse or another graphical IDE with CMake support instead.
ESP-IDF Tools Installer¶
The easiest way to install ESP-IDF’s prerequisites is to download the ESP-IDF Tools installer from this URL:
The installer includes the cross-compilers, OpenOCD, cmake and Ninja build tool. The installer can also download and run installers for Python 3.7 and Git For Windows if they are not already installed on the computer.
The installer also offers to download one of the ESP-IDF release versions. Please choose a directory for downloading ESP-IDF. The recommended directory is
%userprofile% is your home directory. If you do not have it yet, please run the following command to create a new one:
Using the Command Prompt¶
For the remaining Getting Started steps, we’re going to use the Windows Command Prompt.
ESP-IDF Tools Installer creates a shortcut in the Start menu to launch the ESP-IDF Command Prompt. This shortcut launches the Command Prompt (cmd.exe) and runs
export.bat script to set up the environment variables (
IDF_PATH and others). Inside this command prompt, all the installed tools are available.
Note that this shortcut is specific to the ESP-IDF directory selected in the ESP-IDF Tools Installer. If you have multiple ESP-IDF directories on the computer (for example, to work with different versions of ESP-IDF), you have two options to use them:
Create a copy of the shortcut created by the ESP-IDF Tools Installer, and change the working directory of the new shortcut to the ESP-IDF directory you wish to use.
cmd.exe, then change to the ESP-IDF directory you wish to use, and run
export.bat. Note that unlike the previous option, this way requires Python and Git to be present in
PATH. If you get errors related to Python or Git not being found, use the first option.