[Rpm-maint] [rpm-software-management/rpm] Add some cmake-presets(7) and test clang builds in CI (PR #4118)

[Michal Domonkos]

dmnks left a comment (rpm-software-management/rpm#4118)

> Eek, the combination matrix exploded already 😅

Yep, it escalated very quickly indeed :laughing:

> I'd leave the fedora bits out for now, just to keep things simpler for our immediate purposes. We can consider more stuff later.

Ack. I'm thinking I'll drop the other (`release` and `website`) presets as well as I'm not entirely sure *that* is the way we want them to be, it was mostly just the "everything looks like a nail" phenomena :smile: 

> Not to get too deep into bikeshedding, but I'd rather just call sanitizer builds -sanitizer than non-sanitizer fast, because "fast" could also mean a more aggressive optimization level.

Oh, good point. It's only "fast" in the compilation and/or test-suite department, which is quite specific. The other way around works for me, too.

> Another thing is that it's hard to know which of these are meant for the "user" and what are (primarily) just building blocks for other stuff. I'd at least prefix gcc and clang with toolchain- prefix to make it clear that's all they are.
> 
> One possibility might be flagging the building blocks as hidden.

Oh yep, let's make those hidden. I was kinda going to do that but then thought that e.g. `debug` could be useful by itself - except it's typically not the case, indeed, as it's mostly just a building block.



-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/4118#issuecomment-3907952676
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/pull/4118/c3907952676 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20260216/3cd8d29f/attachment.htm>