CONFIG options in cmake file have no effect after updating NCS to 2.5

RE: CONFIG options in cmake file have no effect after updating NCS to 2.5

jonas.woerner — Fri, 03 May 2024 13:54:45 GMT

I just found out that I was doing it wrong all the time, and if doing it right, it does work!

set(CONFIG_MCUBOOT_HEX_FILE "\"${CMAKE_SOURCE_DIR}/my.hex\"" CACHE STRING "blah")

note that the quotes have to be escaped. And what I was missing, was the "CACHE STRING" stuff. It works like that. Thanks to Bell over at Discord for telling me :)

RE: CONFIG options in cmake file have no effect after updating NCS to 2.5

Einar Thorsrud — Fri, 01 Mar 2024 14:07:51 GMT

Hi,

I see the same. We have had a similar case reported before and did some work on it but it is not completed yet. For now I suggest using a fixed path and specifying in prj.conf as that is the only curently supported and working option, but you can look into the mentionned pull request if you really need to work around id (note that this may not make it in even with changes, so there is no guarantee that that approach will work in the future).

RE: CONFIG options in cmake file have no effect after updating NCS to 2.5

jonas.woerner — Tue, 27 Feb 2024 13:51:25 GMT

I just tried it and this sample does work. but try adding set(CONFIG_MCUBOOT_BUILD_STRATEGY_USE_HEX_FILE "y")

this should lead to an error because the hex file is not specified, but with the current version of NCS its just ignored.

RE: CONFIG options in cmake file have no effect after updating NCS to 2.5

Einar Thorsrud — Tue, 27 Feb 2024 13:32:57 GMT

Hi,

There is no way I am aware of to change it. That would be the hack/workaround by specifying the relative path in CMakeLists.txt. Regarding that, while it is not the supported way it should work, and still works for me on version 2.5.2. Can you test on your end, for instance by testing with this unoficial sample?

RE: CONFIG options in cmake file have no effect after updating NCS to 2.5

jonas.woerner — Tue, 27 Feb 2024 13:17:09 GMT

is there a way to change this behaviour? this doesnt really make sense when using a precompiled hex file... Alternatively a fix for the cmake way would also be good. But if the preferred way is to use prj.conf, maybe including an option to force the relative root to prj.conf dir would be a good idea?

RE: CONFIG options in cmake file have no effect after updating NCS to 2.5

Einar Thorsrud — Tue, 27 Feb 2024 12:47:13 GMT

Yes, you are right. It will be relative to mcuboot. From the doc: "...the application directory for relative pathing is considered to be bootloader/mcuboot".

RE: CONFIG options in cmake file have no effect after updating NCS to 2.5

jonas.woerner — Tue, 27 Feb 2024 11:57:02 GMT

so, I tried it but it does not work for me. the relative path is determined from the toolchain directory and not the application source directory... is there a way to change this?

EDIT: Its not the toolchain dir, but the ncs/version/bootloader/mcuboot dir, Is this a bug? as this is the application directory of mcuboot, but only if I were to compile it... as Im using a precompiled version, this directory has nothing todo with my application..

RE: CONFIG options in cmake file have no effect after updating NCS to 2.5

jonas.woerner — Mon, 26 Feb 2024 14:24:03 GMT

ooh thats great, I will try this! thanks!

RE: CONFIG options in cmake file have no effect after updating NCS to 2.5

Einar Thorsrud — Mon, 26 Feb 2024 14:22:25 GMT

That was a problem yes, but you can use relative paths now. This is described in the documentation (search for "relative" here).

RE: CONFIG options in cmake file have no effect after updating NCS to 2.5

jonas.woerner — Mon, 26 Feb 2024 13:46:46 GMT

ok, problem is, I cannot use relative paths in the prj.conf, or can?

RE: CONFIG options in cmake file have no effect after updating NCS to 2.5

Einar Thorsrud — Mon, 26 Feb 2024 13:44:45 GMT

Hi Jonas,

I will look into what has changed. That said, setting these configs in the CMakeLists.txt file has been suggested sometimes, but the proper way to provide tese is in Kconfig files (like prj.conf), so that should be used. (See Adding a bootloader chain).

Einar