Henry Schreiner

Good point. I have the information about platforms (in https://github.com/scikit-build/scikit-build-core/blob/main/src/scikit_build_core/resources/known_wheels.toml ) so could do that, at least as an option.

I think we do the following to make this mostly possible with the new `overrides`. 1. Support `wheel.cmake = False`. This will disable requiring CMake/Ninja during the wheel step too,...

No, I think it's the exact opposite part of the solution. This would give you the ability to enforce the compile based on environment variables. It doesn't handle the try/fail...

See discussion at https://github.com/rapidfuzz/Levenshtein/issues/65 for use case. I think this is what it would look like: ```toml [tool.scikit-build] wheel.cmake = true [[tool.scikit-build.overrides]] if.any.no-system-cmake = "known-wheel" if.any.failed = true wheel.cmake =...

We already support a pure fallback via environment variables. And if you upload a pure Python wheel, that will always be used if a native wheel is not available, no...

We probably need a whole page on overrides rather than just a section; you'd do it with overrides. For example: ```toml [tool.scikit-build] wheel.cmake = false [[tool.scikit-build.overrides]] if.any.env.CIBUILDWHEEL = true if.any.env.CONDA_BUILD...

Overrides page: https://scikit-build-core.readthedocs.io/en/latest/overrides.html

Yes, I’ve done this recently for https://github.com/scientific-python/cookie (based on https://github.com/PyPA/build)

Do you have MSVC inslalled? It looks like you don’t have nmake, which I think means you don’t have a compiler.

Then you probably need to run in the MSVC terminal, or source the MSVC activation script before building. See https://learn.microsoft.com/en-us/cpp/build/building-on-the-command-line?view=msvc-170. CMake does try to find your MSVC install by looking...