pass options to build-backend?

[nschloe]

Not sure if this is the correct repo for the issue.

I'm using Nuitka to build some of my projects and specify it in pyproject.toml via

[build-system]
requires = ["setuptools", "nuitka"]
build-backend = "nuitka.distutils.Build"

I'd now like to pass some options to nuitka.distutils.Build, but I don't know if this is possible at all from build's point of view.

[uranusjr]

By passing options, do you mean pass build-time options that should be decided on build-time (e.g. where to find some external library), or the Build callable simply needs some arguments that you need to pass? For the former you need PEP 517 build options (and you need to ask Nuitka developers how it supports them), and for the latter you need an in-tree build backend to wrap around Nuitka. Either way, this is not a build issue.

[nschloe]

Either way, this is not a build issue.

Definitely not an issue. (Would have opened a gh-discussion, but that's not enabled on the repo yet.)

and for the latter you need an in-tree build backend to wrap around Nuitka

I see! I'll try to work my way through this. Thanks for the advice!

[uranusjr]

It may also be worthwhile to ask if Nuitka is interested in including a PEP 517-compatible module in nuitka itself.

[nschloe]

How would that work? Perhaps I can come up with a PR.

[uranusjr]

You need to implement at least two functions in a module. See PEP 517 specification for the requirements. Once that’s done and included somewhere in nuitka (say nuitka.build_dist), you’d be able to declare a pyproject.toml like this

[build-system]
requires = ["setuptools", "nuitka"]
build-backend = "nuitka.build_dist"

and python -m build will call those two functions under the hood to generate a tar.gz and a whl.

[nschloe]

Nuitka already provides a build-backend here that one can use like

build-backend = "nuitka.distutils.Build"

What's the difference with your suggested approach?

[layday]

The nuitka build backend appears to be a thin wrapper around setuptools so I imagine that you would configure it as you would setuptools.

[FFY00]

Yes, if that is the case, you can use the https://pypa-build.readthedocs.io/en/stable/#python--m-build---config-setting option.

See #328 for eg.
For the implementation side, see https://peps.python.org/pep-0517/#config-settings.

[nschloe]

I'm trying to play around with a local Nuitka version to see of the --config-settings are propagated. How can I tell build to use that local version instead of getting it from PyPI?

[layday]

Run build with the -n flag.