Cristian Le

> But as I understand it, that's what setting `cmake_policy(3.10...4.1)` does, effectively. Yes, that is correct, with the caveat that 1. you can still set them to `OLD` afterwards, and...

`scikit-build-core` is detecting the macos version. For a quick reference, can look at the code around https://github.com/scikit-build/scikit-build-core/blob/3f371fff3d0dd424811ef73f58d88389263d79db/src/scikit_build_core/builder/macos.py#L36 I suspect the failure comes from https://github.com/scikit-build/scikit-build-core/blob/3f371fff3d0dd424811ef73f58d88389263d79db/src/scikit_build_core/builder/wheel_tag.py#L67-L71

If I have a reference test, I could try and add that.

There are a few topics cramped in this issue. - detecting if you are in a temporary build directory. None that I'm aware of. There are also 2 layers of...

> * The primary CMake build-system knows nothing about our python bindings (or scikit-build-core). The system only has some build-recipes the core library, our toy-application examples, and a couple of...

One point that I think would be valuable for you, you can manually set `build-dir` at the CLI level ```console $ pip install -e . -Cbuild-dir=build ``` Then you should...

There are so many ways to handle test-suites, mine are: - pytest for anything related to python running without any build artifacts - gtest/catch etc. for unit-test and integration of...

As a temporary commit for testing purposes, how about pointing `msgspec` to the PR? ```toml msgspec = [ "msgspec @ git+https://github.com/max-muoto/[email protected]; implementation_name == \"cpython\"", ] ```

Were you using `CMAKE_OSX_DEPLOYMENT_TARGET` and something along the lines of [this documentation page](https://scikit-build-core.readthedocs.io/en/latest/configuration.html#configuring-cmake-arguments-and-defines)? CMake's documentation on [`MACOSX_DEPLOYMENT_TARGET`](https://cmake.org/cmake/help/latest/envvar/MACOSX_DEPLOYMENT_TARGET.html) says that it is only used as a default variable for `CMAKE_OSX_DEPLOYMENT_TARGET`. Also,...

> it gets clobbered Not sure what you mean here. It gets removed? We don't alter `CMAKE_OSX_DEPLOYMENT_TARGET` afaict, so if you want to manually override it, you should be able...