Cristian Le

To clarify the issue from the cmake side: - this issue still occurs even when the build directory is specified statically in the configuration? Does Pep517 overwrite the build folder...

Holy smokes that worked. I've enabled the coverage build and changed the build directory and I managed to get test coverage across the python api. Thanks!

So to summarize on what would be nice to have here: - ~~Ability to pass `-DSOME_OPTION` directly~~. Better with `-Ccmake.define.SOME_OPTION` in future pip release - Ability to pass cmake-preset

"directly" as in just passing `-DSOME_OPTION` instead of `--config-settings=...` or `-Ccmake.define.SOME_OPTION`. Is there a potential clash or implementation issue on that?

Oh, I remember some implementation with `setup.py` that basically forwarded any `-D[unknown_flag]` to cmake directly. Is that not possible on the `scikit-build-core` side, only on the user side?

Hmm, if it is not possible, I think the current method is preferred. Just having `-CD.` seems very confusing. I've edited my comment, maybe you can mark this part as...

Btw: ``` gcc: warning: this compiler does not support Arm64 ('-arch' option ignored) ``` My understanding is that cmake needs a toolchain file in order to cross-compile to another architecture....

You can do it through environment variables or specify in the pyproject.toml of cibuildwheel. https://cibuildwheel.readthedocs.io/en/stable/options/#config-settings If there are some defaults baked in for cross-compiling, I am not sure, but @henryiii...

> > this compiler does not support Arm64 > > Pretty sure that means you are dead in the water for cross-compiling to ARM with GCC. I thought that you...

I think this might simply be that there is no implementation for the `gfortran` (maybe fortran in general) for OSX cross-compilation on cmake. You can try your luck on their...