SEGGER Embedded Studio - (output/compiler/*.o): no such file or directory when trying to build the solution.

[hunterzz]

Hello, I just started using a Decawave module running a nRF52 chip. As a starting point, I closely followed the guide provided on the official website, but after doing everything as the guide suggested, when trying to build my solution, the build fails, throwing a `no such file or directory` error. The path provided by the error code is the full path of the project solution (/home/.../examples/dwm-simple/output/compiler/*.o). After some digging around, I found out that one of the most common issues is that there are white spaces in the provided path, but in my case there is none.

My setup includes :

* Linux Mint

* SEGGER Embedded Studio 5.50a

* GNU ARM Embedded Toolchain 5.4 2016q3 (The guide suggested this specific version due to possible compatibility issues)

[Marte Myrvold]

Hi,

Do you have any non English characters in the path? This might cause the same issue as whitespaces.

Best regards,

Marte

[hunterzz]

Hi, no I don't actually. I swapped to my windows-running laptop and it builds just fine, so this issue seems to occur just on Linux. On Windows on the other hand, works out of the box.

[Marte Myrvold]

Hi,

It seems like the problem might be with seeing * as a wildcard. I found a case on the Decawave forum here where someone had a similar problem to yours. In their case the following workaround given by Ryan (in this comment) fixed the issue:

In the ‘Project Explorer’ pane of SES, right click on the Solution and select ‘Options…’
In the Code/External Build section is the Link Command. You will need to edit a part in the middle of this.
Find the snippet that says:
“$(SolutionDir)/output/compiler/*.o”
and edit it to say:
“$(SolutionDir)/output/compiler/$(SolutionName).o”
Leaving all the rest of the command as it is.

Could you try this and see if this fixes your issue? This seems to be an issue related to Decawave's build system or SDK, as I have not seen a similar issue in our SDK where the file that is not found is the compiled object file. If the workaround does not fix your problem, you could also try asking on Decawave's forum.

Best regards,

Marte