Custom board for nRF53 fails to build in SES but builds on commandline

[Kyrre Aalerud]

I created a copy of bluetooth/peripheral example and copied the nRF5340DK board files to make my custom board definitions.
The guideby Øyvind A. Sandberg is really good here although a bit more detail in where you reference the board folder name vs where you reference you app id would be nice.

When I build using west on commandline it all works, but when I use the "open nRF Connect SDK Project" function in SES to generate project files (.emProject) I cannot build result in SES.
Assuming it could be a path issue I moved the proejctfolder to c:\test\ and then it builds in both commandline and SES.

The difference is the name of the build folder in SES is generated based on board name and is 29 characters while the folder when using west on commandline is "build" aka 5 characters.
It has trouble when it comes to the dependencies for cpureset object which has a very long convoluted path.

Is there a workaround for this? I'd rather not have to use the drive root to work in just to avoid a path issue...

[Didrik Rokhaug]

Hi,

The guideby Øyvind A. Sandberg is really good here although a bit more detail in where you reference the board folder name vs where you reference you app id would be nice.

We are happy to hear that you liked it!

For even more information about NCS, I recommend that you read throug this 3 part tutorial/guide: https://devzone.nordicsemi.com/nordic/nrf-connect-sdk-guides/b/getting-started/posts/nrf-connect-sdk-tutorial

The difference is the name of the build folder in SES is generated based on board name and is 29 characters while the folder when using west on commandline is "build" aka 5 characters.
It has trouble when it comes to the dependencies for cpureset object which has a very long convoluted path.

Is there a workaround for this? I'd rather not have to use the drive root to work in just to avoid a path issue...

Unfortunately, Windows has a 256 character file path length limit.

As you are still able to build with West, and it is the name of the build folder that pushes you over the edge, you can simply change the name of the build folder used by SES. This can be done from the "Open nRF Connect SDK Project" dialog box.

Microsoft made it possible to remove this limit a few years ago, but you must still opt-in.

I have not tried this myself, so I can not guarantee that it works with the tools in the toolchain, but you might want to try: https://docs.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation#enable-long-paths-in-windows-10-version-1607-and-later

Best regards,

Didrik