Build error observed with "channel_sounding_ras_initiator" sample application

[Justin Cn]

Dear sir,

I'm using the sample application "channel_sounding_ras_initiator" to performing the evaluation.
Here are my test environment:

- Developement kit: nRF45L151
- Tool chain version: v3.0.2
- SDK version: v3.0.2

But I'm encountering a build error when I tried to build "\v3.0.2\nrf\samples\bluetooth\channel_sounding_ras_initiator":

ninja: error: mkdir(modules/nrf/subsys/nrf_security/src/core/nrf_oberon/CMakeFiles/oberon_psa_core.dir/C_/developers/ncs/v3.0.2/modules/crypto/oberon-psa-crypto/library): No such file or directory
ninja: build stopped: .
FATAL ERROR: command exited with status 1: 'C:\developers\ncs\toolchains\0b393f9e1b\opt\bin\cmake.EXE' --build C:/developers/ncs/v3.0.2/nrf/samples/bluetooth/channel_sounding_ras_initiator/build/channel_sounding_ras_initiator

Here is my build option:


Any ideas for what reason might result in this build error? 

Thanks!

[Elfving]

Hi Justin,

Looks like the default sample and default board then? That is strange. Are you seeing this also with other samples? If a basic sample doesn't build, my first assumption is that there something wrong with SDK installation - so nothing builds.

Regards,

Elfving 

[Justin Cn]

Hi Elfving,

Yes, it's default sample without any modification.
And there is no problem with the other basic sample, such as peripheral UART.
But observing the same problem on both of "channel_sounding_ras_initiator" and "channel_sounding_ras_reflector".
Moreover, I've been install and uninstall SDK several times and install different SDK versions (3.0.0, 3.0.1, 3.0.2).
But the symptom is the same.
By the way, my laptop environment is Windows.

Any ideas for what reason might result in this build error?
Thanks.

[Elfving]

Ah, then I assume the issue is related to the Windows path length. You see windows has this max path length thing, and the name of the channel sounding samples are so long that it likely strikes out on these particular samples and not others.

Could you try either shortening your path length, or what is probably the easiest: give the project a shorter name than the default sample name?

Regards,

Elfving