core is too fat

[crousekimo]

Related area

core library

Hardware specification

esp32-s3

Is your feature request related to a problem?

The esp32 core library is too fat.
It install esp32 esp32-C* esp32-S* and esp32-P* on my computer.
However, I don't need esp32-C* and esp32-P*.
Can I only install the core library for esp32-s3 or esp32?

Describe the solution you'd like

The esp32 core falling into esp32 core, esp32-c* core and esp32-s* core.

Describe alternatives you've considered

No response

Additional context

No response

I have checked existing list of Feature requests and the Contribution Guide

• I confirm I have checked existing list of Feature requests and Contribution Guide.

[SuGlider]

@me-no-dev PTAL.

[lbernstone]

The CI is separated enough now that separate (assets and) packages could be put together for each variant.

[crousekimo]

The CI is separated enough now that separate (assets and) packages could be put together for each variant.

I know that Tools\esp32-arduino-libs\idf-release_v5.4-2f7dcd86-v1\ has separated enough now.
However, are files in Tools\esp-rv32 and esp-x32 for esp32 or esp32-s3?
Can you separated it?
Tools\esp-rv32 has 2.25G now.
Tools\esp-x32 has 1.2G now.
They are too fat.

[lbernstone]

My comment was directed at the devs that the pieces are in place to make single-variant packages. Each toolchain would not get any smaller, you would only download the ones you need.
If you are not using any C or P series devices, you can delete the riscv directories and tar.gz files.

[me-no-dev]

While we have all things separated enough, the Arduino.cc part is not ready to provide proper child cores support. All chip cores must use the main core in order for libraries to properly detect the architecture. That means that the esp32s3 core would be on top of the esp32 core, so that all libs that target esp32 will work for esp32s3. Arduino.cc devs did say that they will be working on this, but it currently does not work and we have no estimate on when that would happen. So for now things will stay as-is. Fat... Toolchain is not that often updated (same goes for the other tools), so version change should mean only downloading the small core and large libs most of the time