Henry Schreiner

Besides cibuildwheel, conda-build/rattler also sets it. If you are not building redistributable wheels, you generally don't need to set it at all, and if you are, you should be using...

My guess is "clobbered" means that when it computes the wheel tag it doesn't look up CMAKE_OSX_DEPLOYMENT_TARGET but just sets the current macOS version as the tag. If you set...

Windows is easy, nothing special is required. :) To be clear, all any of these tools are doing is setting `MACOSX_DEPLOYMENT_TARGET` in the environment. And CMake [supports this](https://cmake.org/cmake/help/latest/variable/CMAKE_OSX_DEPLOYMENT_TARGET.html). And hard...

You have to set this with environment variables to cross-compile. If you hard code it in `tool.scikit-build.cmake.define`, you would make it impossible to build on Intel natively, such as if...

The "developer" produces wheels for common platforms. It's fine to assume they follow standards that work across all backends for those - `MACOSX_DEPLOYMENT_TARGET` is one of the most well documented...

Update: we need to know the wheel tag before we make a build directory, since we allow `build/` as a possible build directory, so asking CMake is out (was thinking...

If you are building from Python, it must always be that version of Python. It's passed through via `PYTHON_EXECUTABLE` at https://github.com/pybind/cmake_example/blob/1017b9029e8dd62f894d84ff0b4abbe5f0bf7dd9/setup.py#L49. I'd recommend considering FindPython over the deprecated FindPythonInterp/Libs, and...

You need to set `Python_EXECUTABLE`; `PYTHON_EXECUTABLE` is for the old search.

What's wrong with passing `-C`? I'd like to focus on things that can't be done, not adding a second way to do things that are already supported. Is the order...

(I'll work on helping with this when I get back from India, sorry for the delay!)