ESP32 Forum

hello,I have some problems when I work with esp-idf V5.2.1.
Some functions before the compilation of the project are confirmed to be not turned on in menuconfig, but after the project is compiled, the corresponding .a file is generated in the build/esp-idf folder, and the corresponding functions are indeed turned on in the sdkconfig file, even after optimizing the compilation level and turning off some log output, the files generated by these useless components occupy a lot of flash space, resulting in a slow online upgrade, how can I completely close these unused components?

Is it possible for each component to have a clear option to enable/disable the component completely?

the files generated by these useless components occupy a lot of flash space

I suggest to check if this is actually the case by running idf.py size-components.

This can be accomplished via cmake. Have a look at the COMPONENTS bullets here: https://docs.espressif.com/projects/esp ... -variables

resulting in a slow online upgrade

Have you changed you baud rate to flash it faster ?

the files generated by these useless components occupy a lot of flash space

I suggest to check if this is actually the case by running idf.py size-components.

Thanks for your response.

You're right, but there are still a few in the stats, and I'm not sure if the project really needs those components.

This can be accomplished via cmake. Have a look at the COMPONENTS bullets here: https://docs.espressif.com/projects/esp ... -variables

Thanks，I will try to check it out.

there are still a few in the stats, and I'm not sure if the project really needs those components.

I don't know either. Those libbt* entries would be Bluetooth code. If you use Bluetooth, you probably need them.
And I wouldn't worry about any components that occupy only a few (kilo)bytes of flash or so at all.

FWIW, the linker does a decent job in removing all entities (functions, variables, constants) from the final binary which are not actually used/referenced by the final application, so the presence or size of a library (.a) is not necessarily indicative of the lib's contribution to flash use/binary size.