The problem I'm reporting is a build/structure problem for a project that resides outside the Nordic SDK.
The project I'm developing involves new boards, new drivers, new libraries. forward involves one application for an nrf9160 module and one for an nrf52832 module. it is very similar to the rather famous "example-application" example related to out of tree development.
My problem is that I can't compile the application correctly and I can't access the root of my repository, where the file zephyr/module.yml is located.
The structure of my project is very similar to the structure of the /nrf folder inside the SDK. Everything is very similar, without the /nrf/toolchain and /nrf/cmake folder, which I don't know if their lack could be responsible for my problem.
this similarity is visible in the following images:
NFR folder:
My personal Out of Tree project:
Compiling the project located inside the /nbiot folder I can't access and compile that are found for example in the driver/sensor/sps30 folder.
In this system the zephyr/module.yml file is not considered as an entry point. The same thing then for the Kconfig and the CMakeLists.txt which are in my root folder.
They are not considered, I can add random characters inside to check for this.
Instead, what is considered in any case is the v1.8.0/nrf/zephyr/module.yml file.
I would like to be able to include my project too, as a module, with the same mechanism where the NRF folder is treated as a module for Zephyr.
Some idea?
The objective of this work is to develop an out of tree project being able to update the SDK, for example to the new current version 2.2.0.
Thank you,
David