Unable to compile cdc_acm with SES 5.30a

[Nicolas Brunner]

Hello, i'm trying to build zephyr\samples\subsys\usb\cdc_acm but i get the following error:

1> zephyr/isr_tables.c does not exist.
1> Combining ‘zephyr/isr_tables.c’
1> C:\Users\nicolas.brunner\ncs\v1.4.99-dev1\toolchain\opt\bin\arm-none-eabi-objcopy.exe: unrecognized option `--output-source'
...
1> C:\Users\nicolas.brunner\ncs\v1.4.99-dev1\toolchain\opt\bin\arm-none-eabi-objcopy.exe: supported targets: elf32-littlearm elf32-littlearm-fdpic elf32-bigarm elf32-bigarm-fdpic elf32-little elf32-big srec symbolsrec verilog tekhex binary ihex plugin
Build failed

With an older SES (5.10d), i have no error during the build.

[Nicolas Brunner]

Apparently SES 5.30a doesn't like to have a "cd" in the project name.

I have also observed that a folder "_acm" appeared to the root of my NCS folder after the failed compilation.

[Øyvind]

Hello, 

I'm currently looking into this. Can you provide more information on your environment? Are you able to provide a full log output from SES? Are you able to build projects using west? I.e. from Toolchain Manager, open bash and try building a project using west?

Edit: What device are you building for?

Thanks! 

Kind regards,
Øyvind

[Øyvind]

Can you please provide screenshots of the "Open nRF Connect SDK project" and Tools -> Options -> nRF Connect?

I am not able to reproduce with Toolchain Manager NCS 1.4.99-dev1. 

 As each install of NCS versions are standalone, sandbox solutions, you should not see this in both NCS 1.4.0 and 1.4.99-dev1. When installing each, are you on VPN or similar?

-Øyvind

[Nicolas Brunner]

The problem also happens with NCS 1.4.0 but it's with the SES of the NCS 1.4.99 with selecting 1.4.0 in the "Open nRF Connect SDK project".

Here are the screen:

I'm generally not using VPN but i can't guarantee that i wasn't using the VPN when i installed NCS.

[Torsten Rasmussen]

Hi Nicolas Brunner,

Could you try to also ask SES to echo the build commands ?


and also attach the `build.ninja` file from a failing build will be helpful.

[Nicolas Brunner]

Here are the files asked :

1830.log2.txt

build.ninja.txt

[Torsten Rasmussen]

Thanks, did some examination, and also managed to reproduce the issue.
I believe this is a long path issue, so could you try to use:

c:\temp\build_nrf52840dk_nrf52840

as the build folder, and see if that helps.