[cbuild] cmse-lib is not always (re-)generated

[MK-HTX]

Steps to reproduce:

1. Build the SimpleTrustZone example.
2. Delete generated CM33_s_CMSE_Lib.o.
3. Rebuild the example.

Expected: CMSE library is recreated and the NS image is successfully rebuilt.

Actual: Build error, missing file and no known rule to make it.

[jkrech]

@MK-HTX can you please confirm that the secure project is also selected in the context set (Manage Solution Settings) and also provide the version of CMSIS-Toolbox that you are using.

[MK-HTX]

Arm Tools:

Project:

origin https://github.com/Open-CMSIS-Pack/csolution-examples (fetch)
commit 0f5a215 (HEAD -> main, origin/main, origin/HEAD)

[jkrech]

Can you please check that the secure project CM33_s is selected in the dialog. Dependencies between the selected contexts get automatically resolved.

Note that the enabled contexts are stored in SimpleTZ.cbuild-set.yml. Since this file is not checked in the repository a default selection is done when the project is loaded in VS Code. It selects one context using the first listed project, the first target-type and the first build-type listed in *.csolution.yml.

[MK-HTX]

It is already selected, as an error is reported when trying to build without it.

[jkrech]

CMSIS-Toolbox problem (cbuild2cmake):

After successful build of the solution I have removed the cmse-lib and ran cbuild again.

C:\projects\GitHub\csolution-examples>cbuild SimpleTrustZone\SimpleTZ.csolution.yml -S
+-----------------------------------------
(1/2) Building context: "CM33_s.Debug+AVH"
Building CMake target 'CM33_s.Debug+AVH'
ninja: no work to do.
+------------------------------------------
(2/2) Building context: "CM33_ns.Debug+AVH"
Building CMake target 'CM33_s.Debug+AVH'
ninja: no work to do.
Building CMake target 'CM33_ns.Debug+AVH'
ninja: error: 'C:/projects/GitHub/csolution-examples/SimpleTrustZone/out/CM33_s/AVH/Debug/CM33_s_CMSE_Lib.o', needed by 'C:/projects/GitHub/csolution-examples/SimpleTrustZone/out/CM33_ns/AVH/Debug/CM33_ns.axf', missing and no known rule to make it
FAILED: CM33_ns.Debug+AVH/src/CM33_ns.Debug+AVH-stamp/CM33_ns.Debug+AVH-build C:/projects/GitHub/csolution-examples/SimpleTrustZone/out/CM33_ns/AVH/Debug/CM33_ns.axf C:/projects/GitHub/csolution-examples/SimpleTrustZone/tmp/CM33_ns.Debug+AVH/src/CM33_ns.Debug+AVH-stamp/CM33_ns.Debug+AVH-build
C:\WINDOWS\system32\cmd.exe /C "cd /D C:\projects\GitHub\csolution-examples\SimpleTrustZone\tmp\2 && C:\Users\jkrech\.vcpkg\artifacts\2139c4c6\tools.kitware.cmake\3.28.4\bin\cmake.exe -E echo "Building CMake target 'CM33_ns.Debug+AVH'" && C:\Users\jkrech\.vcpkg\artifacts\2139c4c6\tools.kitware.cmake\3.28.4\bin\cmake.exe --build C:/projects/GitHub/csolution-examples/SimpleTrustZone/tmp/2"
ninja: build stopped: subcommand failed.
+------------------------------------------------------------
Build summary: 1 succeeded, 1 failed - Time Elapsed: 00:00:05
+============================================================

[MK-HTX]

That's great, you can reproduce.

As a side question, why does it build CM33_s.Debug+AVH twice?

In my actual csolution I have three cprojects and in total building runs six times, with one of the context built three times. Build (2/3) is the golden build with all three projects in the correct order. The other two builds are redundant and a little confusing.