Please upload esp-12.2.0 to platformio registry

[Jason2866]

@antmak to make it possible for developers to adopt Platformio projects to GCC 12.2
Personally i would like to test/support the started Arduino port (based on IDF5.1) with Platformio. Building the framework with Arduino Lib Builder does work. Sadly it cant be used with Platformio since the needed gcc 12.2 toolchains are not available from Platformio registry. (fyi @me-no-dev)

[Jason2866]

ping @antmak @igrr
I would like to support development of the Arduino port based on IDF 5.1 with the IDE Platformio.
Currently it is not possible since the needed 12.2.0 toolchains are not in Platformio registry.

[me-no-dev]

@Jason2866 this needs to be synced with PIO people, because usually it uses the latest toolchain, which will not work with 4.x.

p.s. @valeros @ivankravets

[Jason2866]

@me-no-dev No, uploading to Platformio registry does not break anything or needs adoption in any code. To use the (new) toolchains from registry the user has to change platformio settings (which is easy). One of the nice features of Platformio.
The standard used tools are defined here https://github.com/platformio/platform-espressif32/blob/develop/platform.json

[me-no-dev]

as far as I remember, this was not the case. Let's wait for confirmation and I will upload the toolchain if it will not cause issues (would not be selected and used by folks using ESP-IDF v4.4 or Arduino 2.0.x)

[ivankravets]

@me-no-dev, yes, you can publish the new version of the toolchain. It will not affect existing users.

See the list of dependencies for the latest dev-platform version https://github.com/platformio/platform-espressif32/blob/develop/platform.json#L35

[me-no-dev]

@Jason2866 done

[Jason2866]

@me-no-dev Great, but having problems to install via Platformio. The version scheme used seems to be not the usual Platformio scheme. Can you post the package.json you used?

[ivankravets]

@Jason2866 , thanks for the report. We've just added more strict version validation on our backend infrastructure.

@me-no-dev , could you re-upload all packages and update their version field to conform SemVer specifications? https://semver.org/

If you want to use "date" as a patch component, it will look like 12.2.0+20230208.

P.S.: We will remove previously published packages with broken versions.

[me-no-dev]

Sure! Rebuilding now

[me-no-dev]

@ivankravets any idea what happened here: https://github.com/espressif/arduino-esp32/actions/runs/4742047281/jobs/8420309733?pr=8099#step:4:659

[ivankravets]

@me-no-dev known issue, sorry. @valeros is working on the fix and will come here with updates. You will just need to restart the CI task.

[me-no-dev]

@ivankravets maybe good idea to poke here about going through some of the changes in Arduino v3.0.0 so that we can enable PIO CI again? And that you are aware of what is coming? The main difference is that we now have the SDK as external package installed by Arduino IDE. You have two ways to approach this:

• We make the package PIO compatible
• You package the core yourself on release and include the relevant sdk package already in
• Location of target pio build py is not inside the packaged SDK

@Jason2866 you aware of anything else breaking?

[Jason2866]

@me-no-dev The mentioned points are the ones i have encountered. When the toolchains are in the Pio registry everything looks fine so far. Managed to compile and flash a simple Blink example.

I decided for my (Arduino Lib builder) build process to include the relevant sdk packages in the framework. So it is 100% save that always the correct SDK lib files are used. Would suggest you provide a package with all needed inside for Platformio. The needed changes in Aruino Lib builder to do this are just a few. Did this quick here https://github.com/Jason2866/esp32-arduino-lib-builder/blob/v5.1/tools/archive-build.sh
(Removed some stuff we do not need/use in Project Tasmota...)

[me-no-dev]

@Jason2866 can you post the contents of package.json?

@ivankravets I am getting 504 when trying to upload the new toolchain packages.

pio package publish --non-interactive --owner espressif /Users/ficeto/Desktop/ESP32/pio_packages/out-12.2.0+20230208/toolchain-riscv32-esp-darwin_arm64-12.2.0+20230208.tar.gz
Error: <html>
<head><title>504 Gateway Time-out</title></head>
<body>
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>nginx</center>
</body>
</html>

Preparing a package...
Type:     tool
Owner:    espressif
Name:     toolchain-riscv32-esp
Version:  12.2.0+20230208
System:   darwin_arm64
Size:     86.90MB
The package publishing may take some time depending on your Internet connection and the package size.
Publishing...
pio package publish /Users/ficeto/Desktop/ESP32/pio_packages/out-12.2.0+20230208/toolchain-riscv32-esp-darwin_arm64-12.2.0+20230208.tar.gz failed