Create "debug" and "release" presets that use platform detection

[camio]

${hostSystemName} can be used in CMakePresets.json to decide which toolchain to use based on the host's platform as pointed out in this discussion.

This task is to create generic "debug" and "release" presets that take advantage of this method. Having such presets in place will improve the ergonomics of exemplar's build instructions for new users.

If anyone's interested in working on this and would like a mentor I'd be happy to help.

[wusatosi]

I'd happy to help too for anyone wanting to take this issue, the painful part is probably testing as no one has all three possible platforms.

I would take this if there isn't 15 other issues in beman that I've assigned myself to work on.

[wusatosi]

It seems to be easy to add as a CMakeUserPresets.json

Is there a reason not to add it in CMakePresets.json?

[ClausKlein]

Is there a reason not to add it in CMakePresets.json?

yes, as rapid prototype only yet. May be tested in every beman project I guess.

But you need cmake v3.30 or newer!

Try it, you would have to append the WorkflowPresets.
First, the platform specific presets has to be moved in separate files.

If not, this decrease the readability of the CMakePresets.json even more.

And the readability is not good today!

[ClausKlein]

I have tested the execution project that use this preset on all platforms today. And it works on CI too.

Update, my generic cmake workflow presets were deleted today, so I resign to help!

[dietmarkuehl]

I can concur that the release and debug presets work on all platforms for execution. I started changing the setup to being this project into line with exemplar to eventually get the modules support and adhere to the requirements.

[ClausKlein]

A good entry how Organizing CMake presets

[neatudarius]

@ednolan , is this already implemented?

[ClausKlein]

@ednolan , is this already implemented?

Yes, and No: just each PR to do so was rejected, except on execution!