Daniele Nicolodi

I meant that I see these as two slightly different use cases: one is implementing a solution akin to the RPATH one on Windows, the other is simply having the...

> If you grab build targets from the build dir yourself the end result is not guaranteed to work. There may be e.g. remnants of RPATH in the binaries. If...

> Not to mention that projects that _need_ their post-install scripts to be run in order to work obviously won't work. These projects would indeed not be supported by meson-python,...

> That is because we use special platform dependenct magic to make that happen. It is only undone when doing an `install`. These are the only two supported setups. Yup....

@jpakkane I would appreciate if you could give #551 a spin. You can do that setting ``` [build-system] build-backend = 'mesonpy' requires = ['meson-python@ git+https://github.com/mesonbuild/meson-python.git@refs/pull/551/head'] [tool.meson-python] shared-libs-win32 = true ```...

`ctypes` is not the only way to get a shared library to be useful on Windows. There is also `cffi`. Or the DLL could be linked to an extension module...

`docs/tutorials/entrypoints.rst` is not linked to the documentation index, thus the proposed changes have no effect. Anyhow, I find the proposed addition way to heavy to describe the use of entry...

I think there is some confusion on what is the role of the different directories. There are four relevant directories: the source directory, the build directory, the artifacts directory, the...

> Your description of the various directories sounds right to me. It is not completely right, though. When I wrote it, I was thinking of the case of installing a...

Indeed, that's right. The output looks something like this with pip: ``` $ python -m pip wheel . Processing /Users/daniele/src/meson-python/tests/packages/complex Installing build dependencies ... done Getting requirements to build wheel...