Hello,
I've update my ESP-IDF setup from v3.3 to v5.5.
All worked fine in v3.3, but in V5.5, i'm always the same error compiling my project (using CMD env, Powershell env ou VSCode)
All the build process works fine (i've one the update in my project to be compliant with v5.5), but at the last i've always the same error : cannot open linker script file esp32.peripherals.ld: No such file or directory.
i've checked in component\soc\esp32 and the esp32.peripherals.ld file is in the directorie.
i've try to run ./install.ps1 an ./export.ps1 as i've seen in an other post, but the error still the same.
I've try with the hello world example, and same error.
Thank you in advance for the time you could pass to help me.
cannot open linker script file esp32.peripherals.ld: No such file or directory
Re: cannot open linker script file esp32.peripherals.ld: No such file or directory
Hello,
I've update my ESP-IDF setup from v3.3 to v5.5.
All worked fine in v3.3, but in V5.5, i'm always the same error compiling my project (using CMD env, Powershell env ou VSCode)
All the build process works fine (i've one the update in my project to be compliant with v5.5), but at the last i've always the same error : cannot open linker script file esp32.peripherals.ld: No such file or directory.
i've checked in component\soc\esp32 and the esp32.peripherals.ld is in the directory.
I've tried to compile a sample hello worl project, and error is the same
Error comes always during the action "Linking CXX executable <my project>.
I think that the linker can't find these libraries but all my path seems to be well configured, and at the start of the build process, i can see "-- Adding linker script C:/Users/Eliot/.espressif/frameworks/esp-idf-v5.5/components/soc/esp32/ld/esp32.peripherals.ld"
Thank you in advance for the time you could pass to help me.
Re: cannot open linker script file esp32.peripherals.ld: No such file or directory
Hello,
I may have a clue: if I run CMD or powershell in admin mode, link editing works.
The paths are identical, the properties on the script files are correct, but I really can't figure out what's causing the problem.
Does anyone have any ideas?
Regards
I may have a clue: if I run CMD or powershell in admin mode, link editing works.
The paths are identical, the properties on the script files are correct, but I really can't figure out what's causing the problem.
Does anyone have any ideas?
Regards
Who is online
Users browsing this forum: Bing [Bot], meta-externalagent, Qwantbot and 7 guests