ZEPHYR_BASE dependent paths in NCS CMake- and Kconfig file

[Marwin Bungenstock]

Hello everyone!

This is actually more a suggestion to improve flexibility for NCS integration (i.e. nrf-sdk) into Zephyr workspaces. In many CMake- and Kconfig files there are path references like this:

${ZEPHYR_BASE}/../nrf

If you manage your workspace manually by an app specific manifest file, it is not possible to place nrf-sdk independently from the Zephyr repository on the file system. I think the CMake variable from the root CMakeLists.txt in nrf-sdk could be the better choice.

set(NRF_DIR ${CMAKE_CURRENT_LIST_DIR} CACHE PATH "NCS root directory")

In the current version of the nrf-sdk you are forced to place the srf-sdk next to the Zephyr repo.

Best regards

Marwin

[Charlie]

Hi Marwin,

Thanks for your suggestion. This could be a good solution if you want more flexibility and you are familiar with CMake and Kconfig format.

However, the current NCS folder structure is designed to be fixed and we do not suggest the developer move nrf folder around. The west.yml file contains other dependencies(including zephyr, mbedtls, bootloader and several other libraries) with specific version requirements, it is much convenient to maintain them in the current structure. 

Best regards,

Charlie