Closed camio closed 2 months ago
I think creating presets for a small number of developer-facing workflows makes sense.
Steve is correct that presets files have a hard time really supporting the full space of possible build configurations.
Probably we're going to have to have some discussions and innovate a bit on ways to make development workflows trivial while keeping the files in this project focused on details specific to this project (like project structure) and free of CMake ergonomics per se (like how to do a CMake coverage build).
I think it's fine to value developer ergonomics to keep people productive for now. Steve brought up some approaches we can evaluate as a group going forward.
I think there might be a place for presets, but this PR seems to have lost momentum. If someone else wants to revisit presets later, another PR or issue makes sense.
Reduces the number of steps to build and test. This is incomplete as the .github/workflows was not updated to use it.
The intent is for this commit to generate discussion about moving in this direction.