Master branch. The `-s` and `-t` keys do wrong about esp32-arduino-lib-builder HOT 7 CLOSED

Don't know why this was in the docs but it's now fixed: espressif/arduino-esp32@2075bd4

You can use -t only for specific target

from esp32-arduino-lib-builder.

Don't know why this was in the docs but it's now fixed: espressif/arduino-esp32@2075bd4

Sorry for the stupid question.
If you deleted an erroneous entry in the documentation, then the rest of the problems are solved automatically?
And what about the key -c in the command ./build.sh?
And why in the directory /home/alex/.platformio/packages/framework-arduinoespressif32/tools/ other SoC (esp32, esp32s3, esp32c3) are removed when executing the command ./build.sh -c /home/alex/.platformio/packages/framework-arduinoespressif32/ -t esp32s2?
Did you close the issue because I'm boring and annoying you a lot?

from esp32-arduino-lib-builder.

19 days have passed, and my question remains unanswered...

from esp32-arduino-lib-builder.

-c is meant to replace files in a copy of this repository, not in PIO package. If you want to update your PIO package, you will need to replace the files manually. -t specifies which target to build for, so when you specified only one target, all the others were not built and were not in the replaced structure. The copy script removes the whole tools/sdk folder. -c should not be used with -t, unless that is exactly what you intend.

from esp32-arduino-lib-builder.

Executing the command: ./build.sh -s. Result:

/build.sh: line 162: idf.py: command not found

Not a bug, but a feature?

from esp32-arduino-lib-builder.

-s required IDF to be installed and in your PATH

from esp32-arduino-lib-builder.

-s required IDF to be installed and in your PATH

How is that?
The IDF is already installed by the script build.sh.

from esp32-arduino-lib-builder.