Downloadable Tools
ESP-IDF build process relies on a number of tools: cross-compiler toolchains, CMake build system, and others.
Installing the tools using an OS-specific package manager (like apt, yum, brew, etc.) is the preferred method when the required version of the tool is available. This recommendation is reflected in the Getting Started guide. For example, on Linux and macOS it is recommended to install CMake using an OS package manager.
However, some of the tools are IDF-specific and are not available in OS package repositories. Furthermore, different versions of ESP-IDF require different versions of the tools to operate correctly. To solve these two problems, ESP-IDF provides a set of scripts for downloading and installing the correct versions of tools, and exposing them in the environment.
The rest of the document refers to these downloadable tools simply as “tools”. Other kinds of tools used in ESP-IDF are:
Python scripts bundled with ESP-IDF (such as
idf.py)Python packages installed from PyPI.
The following sections explain the installation method, and provide the list of tools installed on each platform.
Note
This document is provided for advanced users who need to customize their installation, users who wish to understand the installation process, and ESP-IDF developers.
If you are looking for instructions on how to install the tools, see the Getting Started Guide.
Tools metadata file
The list of tools and tool versions required for each platform is located in tools/tools.json. The schema of this file is defined by tools/tools_schema.json.
This file is used by tools/idf_tools.py script when installing the tools or setting up the environment variables.
Tools installation directory
IDF_TOOLS_PATH environment variable specifies the location where the tools are to be downloaded and installed. If not set, IDF_TOOLS_PATH defaults to HOME/.espressif on Linux and macOS, and %USER_PROFILE%\.espressif on Windows.
Inside IDF_TOOLS_PATH, the scripts performing tools installation create the following directories and files:
dist— where the archives of the tools are downloaded.tools— where the tools are extracted. The tools are extracted into subdirectories:tools/TOOL_NAME/VERSION/. This arrangement allows different versions of tools to be installed side by side.idf-env.json— user install options (targets, features) are stored in this file. Targets are selected chip targets for which tools are installed and kept up-to-date. Features determine the Python package set which should be installed. These options will be discussed later.python_env— not tools related; virtual Python environments are installed in the sub-directories. Note that the Python environment directory can be placed elsewhere by setting theIDF_PYTHON_ENV_PATHenvironment variable.espidf.constraints.*.txt— one constraint file for each ESP-IDF release containing Python package version requirements.
GitHub Assets Mirror
Most of the tools downloaded by the tools installer are GitHub Release Assets, which are files attached to a software release on GitHub.
If GitHub downloads are inaccessible or slow to access, it’s possible to configure a GitHub assets mirror.
To use Espressif’s download server, set the environment variable IDF_GITHUB_ASSETS to dl.espressif.com/github_assets. When the install process is downloading a tool from github.com, the URL will be rewritten to use this server instead.
Any mirror server can be used provided the URL matches the github.com download URL format: the install process will replace https://github.com with https://${IDF_GITHUB_ASSETS} for any GitHub asset URL that it downloads.
Note
The Espressif download server doesn’t currently mirror everything from GitHub, it only mirrors files attached as Assets to some releases as well as source archives for some releases.
idf_tools.py script
tools/idf_tools.py script bundled with ESP-IDF performs several functions:
install: Download the tool into${IDF_TOOLS_PATH}/distdirectory, extract it into${IDF_TOOLS_PATH}/tools/TOOL_NAME/VERSION.installcommand accepts the list of tools to install, inTOOL_NAMEorTOOL_NAME@VERSIONformat. Ifallis given, all the tools (required and optional ones) are installed. If no argument orrequiredis given, only the required tools are installed.download: Similar toinstallbut doesn’t extract the tools. An optional--platformargument may be used to download the tools for the specific platform.export: Lists the environment variables which need to be set to use the installed tools. For most of the tools, settingPATHenvironment variable is sufficient, but some tools require extra environment variables.The environment variables can be listed in either of
shellorkey-valueformats, set by--formatparameter:exportoptional parameters:--unsetCreates statement that unset some global variables, so the environment gets to the state it was before callingexport.{sh/fish}.--add_paths_extrasAdds extra ESP-IDF-related paths of$PATHto${IDF_TOOLS_PATH}/esp-idf.json, which is used to remove global variables when the active ESP-IDF environment is deactivated. Example: While processingexport.{sh/fish}script, new paths are added to global variable$PATH. This option is used to save these new paths to the${IDF_TOOLS_PATH}/esp-idf.json.
shellproduces output suitable for evaluation in the shell. For example,export PATH="/home/user/.espressif/tools/tool/v1.0.0/bin:$PATH"
on Linux and macOS, and
set "PATH=C:\Users\user\.espressif\tools\v1.0.0\bin;%PATH%"
on Windows.
Note
Exporting environment variables in Powershell format is not supported at the moment.
key-valueformat may be used instead.The output of this command may be used to update the environment variables, if the shell supports this. For example:
eval $($IDF_PATH/tools/idf_tools.py export)
key-valueproduces output in VARIABLE=VALUE format, suitable for parsing by other scripts:PATH=/home/user/.espressif/tools/tool/v1.0.0:$PATH
Note that the script consuming this output has to perform expansion of
$VARor%VAR%patterns found in the output.
list: Lists the known versions of the tools, and indicates which ones are installed.check: For each tool, checks whether the tool is available in the system path and inIDF_TOOLS_PATH.install-python-env: Create a Python virtual environment in the${IDF_TOOLS_PATH}/python_envdirectory (or directly in the directory set by theIDF_PYTHON_ENV_PATHenvironment variable) and install there the required Python packages. An optional--featuresargument allows one to specify a comma-separated list of features to be added or removed. Feature that begins with-will be removed and features with+or without any sign will be added. Example syntax for removing featureXYis--features=-XYand for adding--features=+XYor--features=XY. If both removing and adding options are provided with the same feature, no operation is performed. For each feature a requirements file must exist. For example, featureXYis a valid feature if${IDF_PATH}/tools/requirements/requirements.XY.txtis an existing file with a list of Python packages to be installed. There is one mandatorycorefeature ensuring core functionality of ESP-IDF (build, flash, monitor, debug in console). There can be an arbitrary number of optional features. The selected list of features is stored inidf-env.json. The requirement files contain a list of the desired Python packages to be installed andespidf.constraints.*.txtdownloaded from https://dl.espressif.com and stored in${IDF_TOOLS_PATH}the package version requirements for a given ESP-IDF version. Althought it is not recommended, the download and use of constraint files can be disabled with the--no-constraintsargument or setting theIDF_PYTHON_CHECK_CONSTRAINTSenvironment variable tono.check-python-dependencies: Checks if all required Python packages are installed. Packages from${IDF_PATH}/tools/requirements/requirements.*.txtfiles selected by the feature list ofidf-env.jsonare checked with the package versions specified in theespidf.constraints.*.txtfile. The constraint file is downloaded withinstall-python-envcommand. The use of constraints files can be disabled similarly to theinstall-python-envcommand.uninstall: Print and remove tools, that are currently not used by active ESP-IDF version.--dry-runPrint installed unused tools.--remove-archivesAdditionally remove all older versions of previously downloaded installation packages.
Install scripts
Shell-specific user-facing scripts are provided in the root of ESP-IDF repository to facilitate tools installation. These are:
install.batfor Windows Command Promptinstall.ps1for Powershellinstall.shfor Bashinstall.fishfor Fish
Aside from downloading and installing the tools into IDF_TOOLS_PATH, these scripts prepare a Python virtual environment, and install the required packages into that environment.
These scripts accept optionally a comma separated list of chip targets and --enable-* arguments for enabling features. These arguments are passed to the idf_tools.py script which stores them in idf-env.json. Therefore, chip targets and features can be enabled incrementally.
Running the scripts without any optional arguments will install tools for all chip targets (by running idf_tools.py install --targets=all) and Python packages for core ESP-IDF functionality (by running idf_tools.py install-python-env --features=core).
Or for example, install.sh esp32 will install tools only for ESP32. See the Getting Started Guide for more examples.
install.sh --enable-XY will enable feature XY (by running idf_tools.py install-python-env --features=core,XY).
Export scripts
Since the installed tools are not permanently added into the user or system PATH environment variable, an extra step is required to use them in the command line. The following scripts modify the environment variables in the current shell to make the correct versions of the tools available:
export.batfor Windows Command Promptexport.ps1for Powershellexport.shfor Bashexport.fishfor Fish
Note
To modify the shell environment in Bash, export.sh must be “sourced”: . ./export.sh (note the leading dot and space).
export.sh may be used with shells other than Bash (such as zsh). However in this case the IDF_PATH environment variable must be set before running the script. When used in Bash, the script will guess the IDF_PATH value from its own location.
In addition to calling idf_tools.py, these scripts list the directories which have been added to the PATH.
Other installation methods
Depending on the environment, more user-friendly wrappers for idf_tools.py are provided:
IDF Tools installer for Windows can download and install the tools. Internally the installer uses
idf_tools.py.Eclipse Plugin includes a menu item to set up the tools. Internally the plugin calls
idf_tools.py.VSCode Extension for ESP-IDF includes an onboarding flow. This flow helps setting up the tools. Although the extension does not rely on
idf_tools.py, the same installation method is used.
Custom installation
Although the methods above are recommended for ESP-IDF users, they are not a must for building ESP-IDF applications. ESP-IDF build system expects that all the necessary tools are installed somewhere, and made available in the PATH.
Uninstall ESP-IDF
Uninstalling ESP-IDF requires removing both the tools and the environment variables that have been configured during the installation.
Windows users using the Windows ESP-IDF Tools Installer can simply run the uninstall wizard to remove ESP-IDF.
To remove an installation performed by running the supported install scripts, simply delete the tools installation directory including the downloaded and installed tools. Any environment variables set by the export scripts are not permanent and will not be present after opening a new environment.
When dealing with a custom installation, in addition to deleting the tools as mentioned above, you may also need to manually revert any changes to environment variables or system paths that were made to accommodate the ESP-IDF tools (e.g.,
IDF_PYTHON_ENV_PATHorIDF_TOOLS_PATH). If you manually copied any tools, you would need to track and delete those files manually.If you installed any plugins like the ESP-IDF Eclipse Plugin or VSCode ESP-IDF Extension, you should follow the specific uninstallation instructions described in the documentation of those components.
Note
Uninstalling the ESP-IDF tools does not remove any project files or your code. Be mindful of what you are deleting to avoid losing any work. If you are unsure about a step, refer back to the installation instructions.
These instructions assume that the tools were installed following the procedures in this provided document. If you’ve used a custom installation method, you might need to adapt these instructions accordingly.
List of IDF Tools
xtensa-esp-elf-gdb
GDB for Xtensa
License: GPL-3.0-or-later
More info: https://github.com/espressif/binutils-gdb
Platform |
Required |
Download |
|---|---|---|
linux-amd64 |
required |
SHA256: d0743ec43cd92c35452a9097f7863281de4e72f04120d63cfbcf9d591a373529 |
linux-arm64 |
required |
SHA256: bc1fac0366c6a08e26c45896ca21c8c90efc2cdd431b8ba084e8772e15502d0e |
linux-armel |
required |
SHA256: 25efc51d52b71f097ccec763c5c885c8f5026b432fec4b5badd6a5f36fe34d04 |
linux-armhf |
required |
SHA256: 0f9ff39fdec4d8c9c1ef33149a3fcdd2cf1bae121529c507817c994d5ac38ca4 |
linux-i686 |
required |
SHA256: e0af0b3b4a6b29a843cd5f47e331a966d9258f7d825b4656c6251490f71b05b2 |
macos |
required |
SHA256: bd146fd99a52b2d71c7ce0f62b9e18f3423d6cae7b2b2c954046b0dd7a23142f |
macos-arm64 |
required |
SHA256: 5edc76565bf9d2fadf24e443ddf3df7567354f336a65d4af5b2ee805cdfcec24 |
win32 |
required |
SHA256: ea4f3ee6b95ad1ad2e07108a21a50037a3e64a420cdeb34b2ba95d612faed898 |
win64 |
required |
SHA256: 13bb97f39173948d1cfb6e651d9b335ea9d52f1fdd0dda1eda3a2d23d8c63644 |
riscv32-esp-elf-gdb
GDB for RISC-V
License: GPL-3.0-or-later
More info: https://github.com/espressif/binutils-gdb
Platform |
Required |
Download |
|---|---|---|
linux-amd64 |
required |
SHA256: 2c78b806be176b1e449e07ff83429d38dfc39a13f89a127ac1ffa6c1230537a0 |
linux-arm64 |
required |
SHA256: 33f80117c8777aaff9179e27953e41764c5c46b3c576dc96a37ecc7a368807ec |
linux-armel |
required |
SHA256: 292e6ec0a9381c1480bbadf5caae25e86428b68fb5d030c9be7deda5e7f070e0 |
linux-armhf |
required |
SHA256: 3b803ab1ae619d62a885afd31c2798de77368d59b888c27ec6e525709e782ef5 |
linux-i686 |
required |
SHA256: 68a25fbcfc6371ec4dbe503ec92211977eb2006f0c29e67dbce6b93c70c6b7ec |
macos |
required |
SHA256: 322c722e6c12225ed8cd97f95a0375105756dc5113d369958ce0858ad1a90257 |
macos-arm64 |
required |
SHA256: c2224b3a8d02451c530cf004c29653292d963a1b4021b4b472b862b6dbe97e0b |
win32 |
required |
SHA256: 4b42149a99dd87ee7e6dde25c99bad966c7f964253fa8f771593d7cef69f5602 |
win64 |
required |
SHA256: 728231546ad5006d34463f972658b2a89e52f660a42abab08a29bedd4a8046ad |
xtensa-esp32-elf
Toolchain for Xtensa (ESP32) based on GCC
License: GPL-3.0-with-GCC-exception
More info: https://github.com/espressif/crosstool-NG
Platform |
Required |
Download |
|---|---|---|
linux-amd64 |
required |
SHA256: 698d8407e18275d18feb7d1afdb68800b97904fbe39080422fb8609afa49df30 |
linux-arm64 |
required |
SHA256: 48ed01abff1e89e6fe1c3ebe4e00df6a0a67e53ae24979970464a4a3b64aa622 |
linux-armel |
required |
SHA256: 0e6131a9ab4e3da0a153ee75097012823ccf21f90c69368c3bf53c8a086736f8 |
linux-armhf |
required |
SHA256: 74173665e228d8b1c988de0d743607a2f661e2bd24619c246e25dba7a01f46bd |
linux-i686 |
required |
SHA256: d06511bb18057d72b555d6c5b62b0686f19e9f8c7d7eae218b712eed0907dbb2 |
macos |
required |
SHA256: 1c9d873c56469e3abec1e4214b7200d36804a605d4f0991e539b1577415409bf |
macos-arm64 |
required |
SHA256: 297249b0dc5307fd496c4d85d960b69824996c0c450a8c92f8414a5fd32a7c3b |
win32 |
required |
SHA256: 858ee049d6d8de730ed3e30285c4adc1a9cdfe077b591ed0b6f2bfa5e3564f53 |
win64 |
required |
SHA256: f469aff6a71113e3a145466d814184339e02248b158357766970646f5d2a3da7 |
xtensa-esp32s2-elf
Toolchain for Xtensa (ESP32-S2) based on GCC
License: GPL-3.0-with-GCC-exception
More info: https://github.com/espressif/crosstool-NG
Platform |
Required |
Download |
|---|---|---|
linux-amd64 |
required |
SHA256: 56e5913b6662b8eec7d6b46780e668bc7e7cebef239e326a74f764c92a3cc841 |
linux-arm64 |
required |
SHA256: 2f0ccc9d40279d6407ed9547250fb0434f16060faa94460c52b74614a38a1e21 |
linux-armel |
required |
SHA256: f71974c4aaf3f637f6adaa28bbbdf3a911db3385e0ab1544844513ec65185cc5 |
linux-armhf |
required |
SHA256: 73e3be22c993f1112fcb1f7631d82552a6b759f82f12cfb78e669c7303d92b25 |
linux-i686 |
required |
SHA256: 504efe97ce24561537bd442494b1046fc8fb9cc43a1c06ef1afa4652b7517201 |
macos |
required |
SHA256: f53da9423490001727c5b6c3b8e1602b887783f0ed68e5defbb3c7712ada9631 |
macos-arm64 |
required |
SHA256: 3592e0fbdb2ca438c7360d93fd62ef0e05ead2fc8144eff344bbe1971d333287 |
win32 |
required |
SHA256: 96b873210438713a84ea6e39e591cdbbeef453cb431d8392ac3fa2e68a48bc97 |
win64 |
required |
SHA256: 9ab0387e08047916bbf7ff0d2eb974c710bcf2e042cb04037b4dd93c9186f676 |
xtensa-esp32s3-elf
Toolchain for Xtensa (ESP32-S3) based on GCC
License: GPL-3.0-with-GCC-exception
More info: https://github.com/espressif/crosstool-NG
Platform |
Required |
Download |
|---|---|---|
linux-amd64 |
required |
SHA256: 5058b2e724166c34ca09ec2d5377350252de8bce5039b06c00352f9a8151f76e |
linux-arm64 |
required |
SHA256: d2c6fb98a5018139a9f5af6eb808e968f1381a5b34547a185f4dec142b0fa44e |
linux-armel |
required |
SHA256: 9944e67d95a5de9875670c5cd5cb0bb282ebac235a38b5fd6d53069813fead9e |
linux-armhf |
required |
SHA256: c0a8836dd709605f8d68ea1fd6e8ae79b3fa76274bfffdd8e79eeadc8f1f3ce1 |
linux-i686 |
required |
SHA256: 0feccf884e36b6e93c27c793729199b18df22a409557b16c90b2883a6748e041 |
macos |
required |
SHA256: 2b46730adc6afd8115e0be9365050a87f9523617e5e58ee35cb85ff1ddf2756c |
macos-arm64 |
required |
SHA256: bb449ac62b9917638b35234c98ce03ddf1cac75c2d80fbd67c46ecec08369838 |
win32 |
required |
SHA256: 0c9ec6d296b66523e3990b195b6597dfc4030f2335bf904b614f990ad6dabbde |
win64 |
required |
SHA256: 7213a0bf22607e9c70febaabef37822c2ae5e071ac53d6467e6031b02bb0b2bf |
xtensa-clang
LLVM for Xtensa (ESP32, ESP32-S2) based on clang
License: Apache-2.0
More info: https://github.com/espressif/llvm-project
Platform |
Required |
Download |
|---|---|---|
linux-amd64 |
optional |
SHA256: b0148627912dacf4a4cab4596ba9467cb8dd771522ca27b9526bc57b88ff366f |
macos |
optional |
SHA256: 1a78c598825ef168c0c5668aff7848825a7b9d014bffd1f2f2484ceea9df3841 |
macos-arm64 |
optional |
SHA256: 1a78c598825ef168c0c5668aff7848825a7b9d014bffd1f2f2484ceea9df3841 |
win64 |
optional |
SHA256: 793e7bd9c40fcb9a4fababaaccf3e4c5b8d9554d406af1b1fbee51806bf8c5dd |
riscv32-esp-elf
Toolchain for 32-bit RISC-V based on GCC
License: GPL-3.0-with-GCC-exception
More info: https://github.com/espressif/crosstool-NG
Platform |
Required |
Download |
|---|---|---|
linux-amd64 |
required |
SHA256: 52710f804df4a033a2b621cc16cfa21023b42052819a51e35a2a164140bbf665 |
linux-arm64 |
required |
SHA256: 812a18f2ecdc3f72c1d098c4e8baa968841099ce9d9ecf95baea85ff71e11013 |
linux-armel |
required |
SHA256: bc6e3ff8323d1f8b137374788b5615152281aab9e7561c55ab1504145677b6c7 |
linux-armhf |
required |
SHA256: 63f85a089fcd06939ed5e7e72ee5cdca590aa470075e409c0a4c59ef1cab3a7b |
linux-i686 |
required |
SHA256: 39d7295c30a23b5ea91baf61c207718ce86d4b1589014b030e121300370f696d |
macos |
required |
SHA256: d3a6f42b02a5f1485ba3fa92b8a9d9f307f643420e22b3765e88bbe4570aee01 |
macos-arm64 |
required |
SHA256: 23d9a715d932a3af57fd7393b0789f88d0f70fedaf5b803deb9ab81dee271bd6 |
win32 |
required |
SHA256: 3e677ef068d7f154d33b0d3788b5f985c5066d110028eac44e0f76b3bda4429b |
win64 |
required |
SHA256: 324a5c679fef75313766cc48d3433c48bf23985a11b5070c5d19144538c6357b |
esp32ulp-elf
Toolchain for ESP32 ULP coprocessor
License: GPL-3.0-or-later
More info: https://github.com/espressif/binutils-gdb
Platform |
Required |
Download |
|---|---|---|
linux-amd64 |
required |
SHA256: b1f7801c3a16162e72393ebb772c0cbfe4d22d907be7c2c2dac168736e9195fd |
linux-arm64 |
required |
SHA256: d6671b31bab31b9b13aea25bb7d60f15484cb8bf961ddbf67a62867e5563eae5 |
linux-armel |
required |
SHA256: e107e7a9cd50d630b034f435a16a52db5a57388dc639a99c4c393c5e429711e9 |
linux-armhf |
required |
SHA256: 6c6dd25477b2e758d4669da3774bf664d1f012442c880f17dfdf0339e9c3dae9 |
linux-i686 |
required |
SHA256: beb9b6737c975369b6959007739c88f44eb5afbb220f40737071540b2c1a9064 |
macos |
required |
SHA256: 5a952087b621ced16af1e375feac1371a61cb51ab7e7b44cbefb5afda2d573de |
macos-arm64 |
required |
SHA256: 73bda8476ef92d4f4abee96519abbba40e5ee32f368427469447b83cc7bb9b42 |
win32 |
required |
SHA256: 77344715ea7d7a7a9fd0b27653f880efaf3bcc1ac843f61492d8a0365d91f731 |
win64 |
required |
SHA256: 525e5b4c8299869a3fdddb51baad76612c5c104bd96952ae6460ad7e5b5a4e21 |
cmake
CMake build system
On Linux and macOS, it is recommended to install CMake using the OS-specific package manager (like apt, yum, brew, etc.). However, for convenience it is possible to install CMake using idf_tools.py along with the other tools.
License: BSD-3-Clause
More info: https://github.com/Kitware/CMake
Platform |
Required |
Download |
|---|---|---|
linux-amd64 |
optional |
https://github.com/Kitware/CMake/releases/download/v3.30.2/cmake-3.30.2-linux-x86_64.tar.gz SHA256: cdd7fb352605cee3ae53b0e18b5929b642900e33d6b0173e19f6d4f2067ebf16 |
linux-arm64 |
optional |
https://github.com/Kitware/CMake/releases/download/v3.30.2/cmake-3.30.2-linux-aarch64.tar.gz SHA256: d18f50f01b001303d21f53c6c16ff12ee3aa45df5da1899c2fe95be7426aa026 |
linux-armel |
optional |
https://dl.espressif.com/dl/cmake/cmake-3.30.2-Linux-armv7l.tar.gz SHA256: 446650c69ea74817a770f96446c162bb7ad24ffecaacb35fcd4845ec7d3c9099 |
linux-armhf |
optional |
https://dl.espressif.com/dl/cmake/cmake-3.30.2-Linux-armv7l.tar.gz SHA256: 446650c69ea74817a770f96446c162bb7ad24ffecaacb35fcd4845ec7d3c9099 |
macos |
optional |
https://github.com/Kitware/CMake/releases/download/v3.30.2/cmake-3.30.2-macos-universal.tar.gz SHA256: c6fdda745f9ce69bca048e91955c7d043ba905d6388a62e0ff52b681ac17183c |
macos-arm64 |
optional |
https://github.com/Kitware/CMake/releases/download/v3.30.2/cmake-3.30.2-macos-universal.tar.gz SHA256: c6fdda745f9ce69bca048e91955c7d043ba905d6388a62e0ff52b681ac17183c |
win32 |
required |
https://github.com/Kitware/CMake/releases/download/v3.30.2/cmake-3.30.2-windows-x86_64.zip SHA256: 48bf4b3dc2d668c578e0884cac7878e146b036ca6b5ce4f8b5572f861b004c25 |
win64 |
required |
https://github.com/Kitware/CMake/releases/download/v3.30.2/cmake-3.30.2-windows-x86_64.zip SHA256: 48bf4b3dc2d668c578e0884cac7878e146b036ca6b5ce4f8b5572f861b004c25 |
openocd-esp32
OpenOCD for ESP32
License: GPL-2.0-only
More info: https://github.com/espressif/openocd-esp32
Platform |
Required |
Download |
|---|---|---|
linux-amd64 |
required |
SHA256: e82b0f036dc99244bead5f09a86e91bb2365cbcd1122ac68261e5647942485df |
linux-arm64 |
required |
SHA256: 8f8daf5bd22ec5d2fa9257b0862ec33da18ee677e023fb9a9eb17f74ce208c76 |
linux-armel |
required |
SHA256: bc9c020ecf20e2000f76cffa44305fd5bc44d2e688ea78cce423399d33f19767 |
linux-armhf |
required |
SHA256: 2cd6436465333e998000b1c311d301b295d8ebaa3fb1c9aa9d4393539dc16ec6 |
macos |
required |
SHA256: 02a2dffe801a2d005fa9e614d80ff8173395b2cb0b5d3118d0229d094a9946a7 |
macos-arm64 |
required |
SHA256: c382f9e884d6565cb6089bff5f200f4810994667d885f062c3d3c5625a0fa9d6 |
win32 |
required |
SHA256: 3b5d615e0a72cc771a45dd469031312d5881c01d7b6bc9edb29b8b6bda8c2e90 |
win64 |
required |
SHA256: 5e7b2fd1947d3a8625f6a11db7a2340cf2f41ff4c61284c022c7d7c32b18780a |
ninja
Ninja build system
On Linux and macOS, it is recommended to install ninja using the OS-specific package manager (like apt, yum, brew, etc.). However, for convenience it is possible to install ninja using idf_tools.py along with the other tools.
License: Apache-2.0
More info: https://github.com/ninja-build/ninja
Platform |
Required |
Download |
|---|---|---|
linux-amd64 |
optional |
https://github.com/ninja-build/ninja/releases/download/v1.12.1/ninja-linux.zip SHA256: 6f98805688d19672bd699fbbfa2c2cf0fc054ac3df1f0e6a47664d963d530255 |
macos |
optional |
https://github.com/ninja-build/ninja/releases/download/v1.12.1/ninja-mac.zip SHA256: 89a287444b5b3e98f88a945afa50ce937b8ffd1dcc59c555ad9b1baf855298c9 |
macos-arm64 |
optional |
https://github.com/ninja-build/ninja/releases/download/v1.12.1/ninja-mac.zip SHA256: 89a287444b5b3e98f88a945afa50ce937b8ffd1dcc59c555ad9b1baf855298c9 |
win64 |
required |
https://github.com/ninja-build/ninja/releases/download/v1.12.1/ninja-win.zip SHA256: f550fec705b6d6ff58f2db3c374c2277a37691678d6aba463adcbb129108467a |
idf-exe
IDF wrapper tool for Windows
License: Apache-2.0
More info: https://github.com/espressif/idf_py_exe_tool
Platform |
Required |
Download |
|---|---|---|
win32 |
required |
https://github.com/espressif/idf_py_exe_tool/releases/download/v1.0.3/idf-exe-v1.0.3.zip SHA256: 7c81ef534c562354a5402ab6b90a6eb1cc8473a9f4a7b7a7f93ebbd23b4a2755 |
win64 |
required |
https://github.com/espressif/idf_py_exe_tool/releases/download/v1.0.3/idf-exe-v1.0.3.zip SHA256: 7c81ef534c562354a5402ab6b90a6eb1cc8473a9f4a7b7a7f93ebbd23b4a2755 |
ccache
Ccache (compiler cache)
License: GPL-3.0-or-later
More info: https://github.com/ccache/ccache
Platform |
Required |
Download |
|---|---|---|
win64 |
required |
https://github.com/ccache/ccache/releases/download/v4.10.2/ccache-4.10.2-windows-x86_64.zip SHA256: 6252f081876a9a9f700fae13a5aec5d0d486b28261d7f1f72ac11c7ad9df4da9 |
dfu-util
dfu-util (Device Firmware Upgrade Utilities)
License: GPL-2.0-only
More info: http://dfu-util.sourceforge.net/
Platform |
Required |
Download |
|---|---|---|
win64 |
required |
https://dl.espressif.com/dl/dfu-util-0.9-win64.zip SHA256: 5816d7ec68ef3ac07b5ac9fb9837c57d2efe45b6a80a2f2bbe6b40b1c15c470e |
esp-rom-elfs
ESP ROM ELFs
License: Apache-2.0
More info: https://github.com/espressif/esp-rom-elfs
Platform |
Required |
Download |
|---|---|---|
any |
required |
https://github.com/espressif/esp-rom-elfs/releases/download/20220823/esp-rom-elfs-20220823.tar.gz SHA256: add4bedbdd950c8409ff45bbf5610316e7d14c4635ea6906f057f2183ab3e3e9 |