Easier method for supporting new board directories

[dboling]

Feature request.

In the current Connect SDK, I must add the name of any new 9160-based board directory to ncs\nrf\cmake\multi_image.cmake.This requires anyone installing the Connect SDK that supports my new board to modify this file. I would rather not require my developers to modify this Nordic-provided file.

A suggestion would be to pull the board names from a list that could be added to before calling ncs/nrf/cmake/boilerplate.cmake in an application's cmakefile.txt.

For example, today I can tell Zephyr to look for board directories by appending to BOARD_ROOT. It would be very nice if there was a NONSECURE_TARGET list that would then be expanded in multi_image.cmake.

Doug

[DevinCallahan]

They changed it in a commit from March 3rd (commit ebe95c364e372627e4616ced0503fd75477bc75c) to pull the nonsecure board name by just removing "ns" from whichever board the "app" target is built with.  You'll need to update to a commit that is newer than that one if you want to avoid modifying multi_image.cmake.

[dboling]

ok Thanks. I expect we'll wait until the next formal release.