App finished, I upgraded now can't build. Which version was my toolchain?

[Albybe]

Hi,

I'm almost crying.... It's one month I'm working on a machine... It works well, It was ready!!!
I have to give this to my boss in two days. (Better in one!)
It's ready. It's finished. (..it was)

Today I tried to encrypt the thing.. many errors flashing...

I had the (wrong!!) idea, I read somewhere I had to update, upgrade linux, than I downloaded ver 4.something of the toolchain... ok, now I cant' build, compile anymore.

My project use WIFI by some common componets, station and AP depending on configuration. NVS, almost all GPIOS... ADC... Freertos Tasks..
I tried some other toolchain versions... each one give me errors, sometimes is wifi defined events (I used some Common_Components), sometimes is bootloader... many different errors.

How can I find which version of ESP-IDF, xtensa I have to install to be able to build and flash again?
Is there a way I can find which version was mine before "destroying it?"

I'm really desperate.

I installed the toolchain last year. But I don't remember exactly when.

I have a backup copy of the linux home directory which include esp directory... can I found something about versions there?

Thanks in advance for any help.

Alby.

[ESP_Sprite]

The version of esp-idf (or at least the Git hash) is printed out when you start the app. If you have a backup directory, you can also run 'git describe' to get the version as well. No idea how you'd get the toolchain version, though, but if you have a backup of the directory it was installed in you can just run something like 'xtensa-esp3-elf-gcc -v' to find out.

[Albybe]

Thank you very much!! ))))

Actually, this night, before my initial post was approved, I """solved""" the problem... I mean, during an asleep night installing every possible IDF version, I ended installing the 3.3, than overwriting my entire esp-idf dir from the original one. Now I can build and flash, as before. ))

(I Just call the boss saying it's almost ready I only have do deal with encrypt again, if I don't get to a solution, I will leave it without encryption.)

I will check versions now as you said, and take note of them!! Thank you very much. ))

Now another question come to my mind: if all the "building/flashing toolchans" are so "variable" and if projects are so dependent from the versions of the toolchain installed (python, xtensa, idf...), do I need different setup or complete different systems for each project?

...because.. if vary something in the system for one project to work, maybe I can "corrupt" another one...

Maybe the answer is to have a virtual machine (something like in virtualbox) for each project with a "working toolchain" inside?

Sorry for my dummy questions, it's about one year I'm developing ESP and STM and in this period I'm getting first two paid contracts (one on ESP the other on STM) and I need to improve my noob knowledge.

Thank you again. I'm breathing now ))))

Alby.

[ESP_Sprite]

The toolchains might/will indeed differ, but if you use the installer or the install.sh script, I think they will be installed in separate directories and esp-idf will know which one to use. If you want to keep a certain version of esp-idf tightly coupled to the project you're working on, it may be helpful to add esp-idf as a submodule to the project.