lack of nrfx_flag32_allocator.c.obj.d and system_nrf5340_network.c.obj.d

[jackie]

Hi ,

IDE: SES

NCS version: 1.9.1

I install the development enviroment following this article. 开发你的第一个nRF Connect SDK(NCS)/Zephyr应用程序 - iini - 博客园 (cnblogs.com)

I use the baidunetdisk to download the NCS v1,9,1. I can compile and run the example except the direction_finding_peripheral. 

Here is the error.

What should I do to solve this error ?

[Sigurd Hellesvik]

Hi

Let me suggest that you go through the things mentioned in Common fixes for nRF Connect SDK build problems.

I suspect that your issue could be related to "3. Windows Path Length"

Regards,
Sigurd Hellesvik

[ARearden]

Hi Sigurd, 

I have modified the SDK path to C:/ncs/ and also have my project directory in the C: drive under the shortest path possible but still have this issue.

Adam

[Vidar Berg]

Hi Adam,

I'm  a bit surprised you see the same issue after shortening the project paths. Please check if your build log maybe still shows the CMAKE_OBJECT_PATH_MAX warning you had earlier:

C:/StrAPs_fw/ecg-python-model-main-FW-ADC_uSD-StrAPs_prototype-threads/FW/ADC_uSD-StrAPs_prototype/threads/build_strapsprot/modules/hal_nordic/nrfx/CMakeFiles/modules__hal_nordic__nrfx.dir/./

has 191 characters. The maximum full path to an object file is 250
characters (see CMAKE_OBJECT_PATH_MAX). Object file

C_/ncs/v1.9.1/modules/hal/nordic/nrfx/helpers/nrfx_flag32_allocator.c.obj

cannot be safely placed under this directory. The build may not work
correctly.

Alternatively, if you are have Win10  (build code >1607), you may try to just disable the path length limit instead: https://docs.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=cmd#enable-long-paths-in-windows-10-version-1607-and-later.