b354c11db7
Linker script generator produces build/esp32/esp32.common.ld from components/esp32/ld/esp32.common.ld.in This works fine until IDF is downgraded to V3.1 which uses components/esp32/ld/esp32.common.ld and doesn't track build/esp32/esp32.common.ld at all. At this point, the linker runs in the build/esp32 directory and "-T esp32.common.ld" picks up the linker script generated .ld file, which causes mis-builds. As reported on forums: https://esp32.com/viewtopic.php?f=13&t=9684&p=40105 |
||
---|---|---|
.. | ||
elf_to_ld.sh | ||
esp32.extram.bss.ld | ||
esp32.ld | ||
esp32.peripherals.ld | ||
esp32.project.ld.in | ||
esp32.rom.ld | ||
esp32.rom.libgcc.ld | ||
esp32.rom.nanofmt.ld | ||
esp32.rom.redefined.ld | ||
esp32.rom.spiflash.ld | ||
esp32.rom.spiram_incompatible_fns.ld | ||
esp32_fragments.lf |