EIM-79 discovery of existing idf installations #102
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Important Installation incomplete: to start using Gemini Code Assist, please ask the organization owner(s) to visit the Gemini Code Assist Admin Console and sign the Terms of Services. |
Hahihula
force-pushed
the
EIM-79-discovery
branch
3 times, most recently
from
0eeeefa to
e9f1180
Compare
Hahihula
changed the title
Hahihula
force-pushed
the
EIM-79-discovery
branch
7 times, most recently
from
01c32b3 to
0cc3eb1
Compare
Hahihula
force-pushed
the
EIM-79-discovery
branch
13 times, most recently
from
8a4cd87 to
f4c5c90
Compare
Hahihula
force-pushed
the
EIM-79-discovery
branch
4 times, most recently
from
97eb695 to
de9d7bd
Compare
Hahihula
force-pushed
the
EIM-79-discovery
branch
from
59a905c to
c57a54a
Compare
Hahihula
force-pushed
the
EIM-79-discovery
branch
from
a714c5d to
b3659af
Compare
|
I've tested with eim cli linux x64 I have 2 versions defined in esp-idf.json that i installed with older vscode setup. Running the eim discover does indeed find the setups and add them to eim_idf.json. The activation script does seems to have issues. Please review my Ubuntu terminal output. Here is my PATH in a different terminal Regarding the second setup that was found, it seems to be working properly. Here is the steps and output i've used for testing it: |
Hahihula
force-pushed
the
EIM-79-discovery
branch
from
b3659af to
7ef7f72
Compare
Hahihula
changed the title
Hahihula
force-pushed
the
EIM-79-discovery
branch
3 times, most recently
from
c253671 to
69c8f6f
Compare
Hahihula
changed the title
|
Can we show the ESP-IDF path next to the version? I see that EIM has detected multiple instances of the same ESP-IDF version, likely because I installed them in different folders. It’s hard to distinguish which version points to which folder. 
Same during the selection as well |
|
I see it's detected ESP-IDF 4.x versions as well. Do we need to show them, considering we don't support them? |
ok, good point, but i would like to do it in separate ticket if it's ok with you To the 4.X version, the discovery is meant to import every existing version available on user system, if he has some projects still relying on the older version, we should probably not cut them off them |
|
We can remove "(not implemented yet)" from the command 
|
Ahh... Thanks for the catch! |
The challenge here is - Espressif-IDE doesn't work with 4.x anymore, we need to have 5.0 and higher |
kolipakakondal
approved these changes
Jul 25, 2025
|
Thank you for the changes. After deleting the .espressif directory. I proceed to use eim install from eim-cli-linux-x64-650 to install esp-idf 5.5. The results are unfortunately the same. Although the scripts are generated, the resulting path doesn't seem to work for blink build on each IDF_PATH example for one of the ESP-IDF setups. Use of EIM discovery and v5.4.2 activation script and blink build. TL;DR Works well Use of ESP-IDF v5.1.6 activation script and blink build. Please consider that i previously installed v5.5 using EIM and this is already added in eim_idf.json. Interesting enough, seems that xtensa-esp32-elf-gcc used for the EIM provided version is totally the same: |
Hahihula
force-pushed
the
EIM-79-discovery
branch
from
079f877 to
9af370a
Compare
Hahihula
force-pushed
the
EIM-79-discovery
branch
6 times, most recently
from
07d7535 to
4e42c60
Compare
IDF installed using eim or eclipse can be discovered parsing function for esp_idf.json file added POSIX discovery mvp updated activation script creation improved export paths in old version discovery added tool_set.json file parsing to the discovery returned the parse_tool_set_config back to working state updated according to changes in the scripts location Documentation update to add the discovery command reworked the vscode discovery according to new approach to isntallation removed unused code updated the discovery command help Fixed discovery tools paths improved windows debugging part of discovery and venv creation creating venv using proper python discovery disabled for vscode installed IDF on windows
Hahihula
force-pushed
the
EIM-79-discovery
branch
from
4e42c60 to
f9d20bb
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adds the discovery command which will scan the filesystem for existing idf instances and will try to add them to the eim_idf.json file. But it will not fix them, so if it's just repository which was not installed, it will not work.
Supports the discovery of IDF installed previously by VScode.
Supports the discovery of IDF installed previously by Espressif IDE.
documentation updated
rebased
rebased again
rebased on top of new changes
rebased on top of the deduplication fix
waiting for #163 which solves the eclipse issue
rebased on top of last release
rebased on top of 0.2.8
rebased and tested
Related
Testing
Tested discovery of previously instaled IDF using vscode on macos. Sucesfully builded hello world.
Tested discovery of previously instaled IDF using eclipse on macos. Sucesfully builded hello world.
Checklist
Before submitting a Pull Request, please ensure the following: