For anyone who would ran into the same issue: The wildcards in the command line arguments (*, ? for e.g.) are not extended within the programs (in our case the gcc) but in the shell processing it. In the case of SES I do not know how it is used, however the star extending to separate arguments based on the available file list does not work. I "workarounded" it by passing the command to bash in the build steps like: Shell-Script (1 line)
It looks to be a sequencing issue: Modifying the linker command to have a sleep 1 before the actual linker command allows the linker to run properly: imgur.com/a/krEfQbs It still does not understand why the build fails this way, but still investigating.
I am trying to build a Nordic nRF based project with SES 5.60a however I got the following linker error: imgur.com/a/gQo7DYW The object files are visible and readable by the SES itself: imgur.com/a/LJN76SD If I ran the linker command from a terminal the linker runs fine and produces the outputs: imgur.com/a/VVr8I53 I ran the SES with the same user as I ran in terminal. I have also tried to run SES with sudo but the results are the same. I am running a stock Ubuntu 20.04 I tried to disable apparm…