Problems with long path lengths (CMAKE_OBJECT_PATH_MAX errors)

RE: Problems with long path lengths (CMAKE_OBJECT_PATH_MAX errors)

Burt — Mon, 16 Feb 2026 19:16:18 GMT

Hopefully Priyanka will answer your question, Greg. It took me a while to recall that I had changed the name nrf_cloud_multi_service to ncms in order to build, back in v2.8.0 time frame.

Burt

RE: Problems with long path lengths (CMAKE_OBJECT_PATH_MAX errors)

Greg Feeney — Mon, 16 Feb 2026 17:29:35 GMT

I'm using version 3.1.0 of the SDK on Windows 11 and encountering this same path name length restriction. Is it still a limitation of the Zephyr environment(version 4.1.99) or has there been some development efforts made to remove or override the 250 character restriction?

RE: Problems with long path lengths (CMAKE_OBJECT_PATH_MAX errors)

Burt — Wed, 20 Nov 2024 05:20:27 GMT

Hi Priyanka, I am having this same issue trying to build nrf_cloud_multi_service. I don't like the suggestion to restructure the project or do anything unusual as I have set up my system in the standard way and so the path the Nordic SDK has provided me is

C:\ncs\v2.8.0\nrf\samples\cellular\nrf_cloud_multi_service>

The onus should be on the SDK developers rather than me to come up with workable paths, I would think. Thanks, Priyanka. --Burt

RE: Problems with long path lengths (CMAKE_OBJECT_PATH_MAX errors)

Ben_Squar3d — Thu, 11 Jul 2024 10:02:20 GMT

Hi, thank you for you answer

RE: Problems with long path lengths (CMAKE_OBJECT_PATH_MAX errors)

Priyanka — Thu, 11 Jul 2024 07:46:44 GMT

Hi,

The problem is that the maximum full path length for an object file is defined as 250 characters in the Zephyr build system. So I'm afraid the CMAKE_OBJECT_PATH_MAX setting in the local CMakeLists.txt file won't affect the global setting used by Zephyr's build system since each CMakeLists.txt file has its own scope, and changes in one don't affect others. So the solution is to reduce the path length and if this is not possible, you might need to maybe restructure your project in order to try reducing the path length (or maybe even try using symbolic links). I understand that this is not quite a feasible option, but I'm sorry for the trouble.

-Priyanka

RE: Problems with long path lengths (CMAKE_OBJECT_PATH_MAX errors)

Ben_Squar3d — Wed, 10 Jul 2024 12:30:50 GMT

Hi, sorry to hijack the post but I face the exact same issue. Was it addressed in the meatime?

RE: Problems with long path lengths (CMAKE_OBJECT_PATH_MAX errors)

Priyanka — Wed, 19 Jul 2023 13:33:47 GMT

Hi Sandeep,

I will discuss this internally with my colleagues and get back to you. Please expect a slight delay as we are currently short staffed due to the summer holidays here in Norway.

Thank you for your patience and understanding.

-Priyanka

RE: Problems with long path lengths (CMAKE_OBJECT_PATH_MAX errors)

swlnk — Tue, 18 Jul 2023 17:18:23 GMT

Hi Priyanka-

>> Which sample are you working on, i.e. is it a custom sample?

It is a custom application within our own git repo (i.e. the project directory is not located within the NCS / Zephyr installation)

>> Also, which board are you working on?

We are building for the nRF5340DK (nrf5340dk_nrf5340_cpuapp)

>> Are you trying to build via VSCode or west?

I'm using nRF Connect for VS Code v2023.6.345, Running on Windows 10. I'm building by clicking the "Build" button under "Actions" in the VS Code plugin.

RE: Problems with long path lengths (CMAKE_OBJECT_PATH_MAX errors)

Priyanka — Tue, 18 Jul 2023 05:48:22 GMT

Hi Sandeep,

Which sample are you working on, i.e. is it a custom sample? Also, which board are you working on? Are you trying to build via VSCode or west?

Best Regards,

Priyanka