Permissive project list for csolution.yml

[slhultgren]

It would be very nice if the tooling could allow csolution.yml project list to include all projects necessary. (The schema only specifies that the project should contain path to the project file, format unspecified)

For example it should be possible to link to a CMakeLists.txt or MyCustomProject.
In this case Open-CMSIS tooling would ignore those unknowns and only care about the files that it recognizes, e.g. *.cproject.yml, *.csolution.yml, *.clayer.yml.

[jkrech]

  projects:
    - project: ./App/app.cproject.yml
    - project: ./MySubmodul/CMakeLists.txt
    - project: ./MyCustomProject/MyProject.xyz

I assume that some other tool will be able to make sense of the project format being referenced and actually consider these files.
Should the Open-CMSIS tooling even attempt to build the solution? Isn't it likely that the build will fail without the artifacts created by the "unknown" projects?

[ReinhardKeil]

I think this is covered by https://github.com/Open-CMSIS-Pack/devtools/blob/main/tools/projmgr/docs/Manual/YML-Input-Format.md#prepost-build-steps

This just needs to be implemented

@slhultgren could you review and provide feedback?

[ReinhardKeil]

@brondani are the prepost-build-steps already implemented?

[jkrech]

@ReinhardKeil , no pre- and post-build steps are not supported yet.

[brondani]

From the #prepost-build-steps:

Tbd: potentially map to CMake add_custom_command.

Since this would require further CPRJ extensions I would rather plan the full CPRJ deprecation and implement the new CMakeLists generation before implementing prepost-build-steps.