[EDITED after more investigation]
I am using workflow 4, where I have my own application's manifest "west.yml" (See https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.5.0/nrf/dm_adding_code.html#workflow-4-application-as-the-manifest-repository)
The file structure is like this:
application
├── bootloader
│ └── mcuboot
├── manifest
│ └── west.yaml -> my own west.yml, which imports nrf-sdk and where 'mcuboot' is defined as a project, too
├── nrf
│ └── west.yaml -> ncs's west.yml, which is being "imported" (which also contains the 'mcuboot' project)
When overriding the "mcuboot" project inside my own west.yaml, I cannot seem to properly build a multi-image hex including MCUboot anymore.
Simple test project, on ncs v1.5.0:
This results in:
CMake Error at /home/vinz/Work/git/snt_zephyr/nrf/modules/mcuboot/CMakeLists.txt:112 (add_child_image):
Unknown CMake command "add_child_image".
Full terminal output:
I am on Arch Linux, with CMake 3.19.7.
I tried using ARM GCC Embedded, Zephyr SDK 0.11.3, 0.12.3, but to no avail.
Also tried to remove zephyr cache (rf -rf ~/cache/zephyr), but the result is the same.
When I remove my own "mcuboot" project from my west.yml, and therefor the one imported from nrf/west.yml is used instead, everything works as expected.
Except of course, then I cannot use my custom "mcuboot" softfork.
Is this a known issue? How can I use my own "mcuboot" softfork, without having to fork the "nrf-sdk" repo as well?