Relative paths or Workspace paths in "Other objects"
01/18/2021 | 10:58 PM
Using Simplicity Studio SV4.1.13.9
I'd like to use a Workspace relative path in "Other objects"
"./BL652/autorun.o" doesn't work.
${workspace_loc:/${ProjName}/BL652/autorun.o} fails at the link stage with:
arm-none-eabi-gcc.exe: error: D:DocumentsProductsForceDecksFDV2FirmwareWorkingFDV2BL652autorun.o: No such file or directory
Discussion Forums
Simplicity Studio
Answered
Answered
Hi Damon,
It looks like it is an issue with the slashes being removed from the path. Are you specifying the link as ${workspace_loc:/${ProjName}/BL652/autorun.o} - (without quotes) and not "./BL652/autorun.o"?
For instance a Bluetooth project specifies several files that way:
And the linker output shows the paths correctly expanded.
If I put double quotes around the path for the first library I get a similar error as you are seeing:
arm-none-eabi-gcc.exe: error: D:v4_ws_testsoc-thermometerplatformradiorail_libautogenlibrail_releaselibrail_config_mgm210pa32jia_gcc.a: No such file or directory
Relative paths or Workspace paths in "Other objects"
Using Simplicity Studio SV4.1.13.9
I'd like to use a Workspace relative path in "Other objects"
"./BL652/autorun.o" doesn't work.
${workspace_loc:/${ProjName}/BL652/autorun.o} fails at the link stage with:
Hi Damon,
It looks like it is an issue with the slashes being removed from the path. Are you specifying the link as ${workspace_loc:/${ProjName}/BL652/autorun.o} - (without quotes) and not "./BL652/autorun.o"?
For instance a Bluetooth project specifies several files that way:
And the linker output shows the paths correctly expanded.
If I put double quotes around the path for the first library I get a similar error as you are seeing:
arm-none-eabi-gcc.exe: error: D:v4_ws_testsoc-thermometerplatformradiorail_libautogenlibrail_releaselibrail_config_mgm210pa32jia_gcc.a: No such file or directory
I hope this helps.
Thank you,
jpitt
That works!.
Thanks