Daniel Schürmann

This is a duplicated of https://github.com/mixxxdj/mixxx/issues/6493

We can keep both open. You may do a research whether there are FOSS libraries that can do it or implemqtations we can copy from.

Here some thoughts: The long list of flags in the workflow files is sourced by the idea to make every possible option visible. On the user machine all of them...

LOCALECOMPARE should be ON for all. This should be already the case by the main CMakeList.txt the only case where this is not set is of you build on Apple...

> So can we specify it explicitly in the Presets to ON or will that cause a hard fail in the dynamic case for macOS? I think yes.

> I have a debug config for development and a release config I use to install betas from my fork. What is special about it in your case? Normally we...

The current solution has the disadvantage that it is tempting to use this at home or in the build system of various distros. Even though it should IMHO not be...

> If they were internal and correct by default, we shouldn't have had to specify them on CI in the first place They have been artificially added. In case of...

> CMakePresets being relatively smart and expressive I consider this a maintenance burden to have on one hand smart defaults in CMakeList.txt, override it with preset and add another layer...

Back to this PR: * The idea to describe our configs in a preset is a good idea. * If we provide a minimal config for home builds and package...