Specifying components in package.metadata.esp-idf-sys fails the build
#319
Comments
|
while that technically should cross import all non specified components recursively through REQUIRES or PRIV_REQUIRES flag, it could create a case where for example "technically" bt doesn't require the "main" component and so for. So in that case you could miss something here that we assume to always be there. I would in your shoes check out what "default" components we use and manual include the ones that seams pretty substatial to explicitly included by you. For example on a s3 the default list on a "hello-world" is something like "bootloader bootloader_support efuse esp_app_format esp_bootloader_format esp_common esp_hw_support esp_rom esp_system esptool_py freertos hal log main micro-ecc newlib partition_table soc spi_flash xtensa" You can try to add them all and add your bt component and try to delete stuff from that list and check when it breaks. You can find the list of included components in the "output" file that is create in the buildoutput inside the esp-idf-sys build dir |
|
I had the exact same issue as the OP. I did @Vollbrecht's suggestion and checked the default component list in Adding that entire list fixed it for me and then I was able to winnow it down to just "main" to resolve the problem. In my case I also have extra_components in the |
What does "just main" mean exactly for your concrete case? |
|
@ivmarkov Here's the section from Cargo.toml. If I omit |
When generating a new blank template from https://github.com/esp-rs/esp-idf-template and adding any number of components in
package.metadata.esp-idf-sys, the build fails withI'm not sure wether this error also occurs in projects where just
esp-idf-sysis used.Cargo.toml:Cargo build -vv log:
log.txt
Is this related to
binstartin some way?I found this bug when trying to limit included components to reduce binary size.
The text was updated successfully, but these errors were encountered: