Henry Schreiner

I'm working around this for now in https://github.com/scikit-build/scikit-build-core/pull/303. Not extremely happy with the workaround, so still would like to work out if this the expected behavior from CMake.

FYI, maturin and now hatchling are producing metadata 2.3.

Small comment: Hatchling is the third most popular build backend on PyPI (after setuptools and Poetry) - it's the most popular backend to only support PEP 621 and maturin is...

I take it the current status is that you can't "inject" wheels that can be loaded with a simple import, like the pre-built pyodide wheels? Adding wheels to `/pypi` doesn't...

No colon, that's only for tests - universal wheels needed a way to skip the either of the two possibilities when testing, so there's a colon for `test-skip` (and only...

Could you add: ```toml [tool.scikit-build] cmake.verbose = true logging.level = "INFO" ``` So we can see a bit more about what's happening?

It won’t build with conflicts, unfortunately.

Yes, looks like a bug on my end: ``` 2024-03-21 14:54:34,003 - scikit_build_core - DEBUG - Windows ARM targeted via SETUPTOOLS_EXT_SUFFIX 2024-03-21 14:54:34,003 - scikit_build_core - INFO - Reading DIST_EXTRA_CONFIG:build_ext.library_dirs=C:\Users\runneradmin\AppData\Local\pypa\cibuildwheel\Cache\nuget-cpython\pythonarm64.3.11.8\tools\libs...

No, wait, that does say `arm`. Not sure why I thought it said `amd` or something. But I think that's the wrong form, I think it should be `cpython-312-win_arm64`.

Wow, I knew the linux ones were coming, a bit of a surprise the Windows ones came too. That’s great. Going to be a little tricky to test though until...