uv2csolution executes cbuild setup twice

[ReinhardKeil]

Execute uv2csolution using context menu in Explorer View runs cbuild setup twice.

Use this project: test.zip

uv2csolution.exe c:\Test\Jan10\10872\test.uvprojx
1 out of 1 target(s) converted
Created solution: C:/Test/Jan10/10872/test.csolution.yml
With projects:
- C:/Test/Jan10/10872/test.cproject.yml
Enqueue: cbuild setup c:\Test\Jan10\10872\test.csolution.yml --context-set --packs
Execute: cbuild setup c:\Test\Jan10\10872\test.csolution.yml --context-set --packs
C:/Test/Jan10/10872/test.csolution.yml:2:3 - error csolution: schema check failed, verify syntax

Completed: cbuild failed with exit code 1
Enqueue: cbuild setup c:\Test\Jan10\10872\test.csolution.yml --context-set --packs --update-rte
Execute: cbuild setup c:\Test\Jan10\10872\test.csolution.yml --context-set --packs --update-rte
C:/Test/Jan10/10872/test.csolution.yml:2:3 - error csolution: schema check failed, verify syntax

Completed: cbuild failed with exit code 1

[JonatanAntoni]

Cannot reproduce.
Whats the reason behind the error message

C:/Test/Jan10/10872/test.csolution.yml:2:3 - error csolution: schema check failed, verify syntax

Another observation we need to clarify:

uv2csolution --version
uv2csolution version 1.5.0 (C) 2022-2024 Arm Ltd.

Creates two set of files for Target_1 and Target1.

[JonatanAntoni]

@mguzmanm, could you have a look into this UV project and if the conversion results are as expected, please?

[ReinhardKeil]

@JonatanAntoni @mguzmanm we verify this again once the uv2csolution is final. The problem is that the internal test versions set "version" to "unknown".

[jkrech]

I am still able to reproduce that cbuild setup is invoked twice (on windows) even with a uv2csolution 1.6.0 / 1.6.0-RC1.
This needs further investigation. As it does not create any damage I am rescheduling to next release.

[ReinhardKeil]

The reason why uv2csolution is triggered twice is that initially there is no *.cbuild-set.yml file. I would argue that generating the *.cbuild-set.yml file by cbuild itself should not trigger another cbuild run.

I did start the conversion by using the context menu in the Explorer view. This has the following issues:

• As the user does not get feedback, I clicked the option twice. This caused the 2 times execution of uv2csolution. When no tools are loaded (and on my slow computer) it takes a while until the conversion is completed. This caused confusion on my end.
• There is also no notification that the *.csolution.yml file exists already. This means that modifications are potentially overwritten.