mirror of
https://github.com/espressif/esp-idf.git
synced 2025-08-08 04:02:27 +00:00
esp32: Rename esp32.common.ld to esp32.project.ld to avoid build errors when downgrading
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
This commit is contained in:

committed by
Angus Gratton

parent
710bcbd447
commit
a79c5b8271
@@ -539,7 +539,7 @@ lives under ``$(IDF_PATH)/tools/ldgen``.
|
||||
|
||||
Linker Script Template
|
||||
^^^^^^^^^^^^^^^^^^^^^^
|
||||
Currently, the linker script template used is :component:`esp32/ld/esp32.common.ld.in`, and is used only for the app build. The generated output script is
|
||||
Currently, the linker script template used is :component:`esp32/ld/esp32.project.ld.in`, and is used only for the app build. The generated output script is
|
||||
put under the build directory of the same component. Modifying this linker script template triggers a re-link of the app binary.
|
||||
|
||||
Linker Fragment File
|
||||
|
Reference in New Issue
Block a user