Henry Schreiner

PS: I also plan to add an overrides system similar to the one I put in cibuildwheel, and once that's in place, some configuration for the generator would suddenly be...

> It looks like ninja is not used on my Mac when I use the current version of scikit-build-core. FYI, the 0.4.x series includes a fix for a logic problem...

Config settings are something entirely processed by build backends. They have no meaning to plugins. Scikit-build-core choses to make config settings look like pyproject.toml settings and uses them for overrides,...

I don't think hatch allows overriding from config settings either. The idea is that if setuptools_scm had a full plugin with dynamic-metadata options (instead of a custom tool section), then...

I'll look into this a bit more soon, but just to let you know, as of `scikit-build-core` 0.3, we support third party packages supplying CMake files. You could make a...

@bennyrowland - I've added you so you should be able to edit the proposal above. What do you think? Let's get a few others involved once it looks good.

Okay, edited edited version above. We need to pick a method for local plugins (and add it to the reference implementation).

Just noticed `swig` also has a binary distro on pypi. That's another package where only including it if it's not already installed would be useful (and one that's not directly...

The hook is implemented by plugins (setuptools_scm, for example). But the handling of the hook would be implemented by backends. Frontends would not be affected. It would be up to...

I was actually already making that change, since I wanted a `path=` key. How about the following changes on top of 2a: * Keys in `dynamic-metadata` are implicitly implied to...