Jussi Pakkanen

> the wheel for CapyPDF 0.5.0 includes a few executables that I'm fairly sure fail to load the required DLLs when executed on Windows. Those executables should not be there...

Things get even weirder now. With CapyPDF 0.7.0 and meson-python 0.13.2 on Windows the `--skip-subprojects=lcms2` argument seems to be ignored and the executables from that subproject get in the package...

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 you...

Not to mention that projects that _need_ their post-install scripts to be run in order to work obviously won't work.

> Meson itself supports running build artifacts from the build directory via the test() facility. That is because we use special platform dependenct magic to make that happen. It is...

I tried it and it seems to be working. Thanks. > Suggestions for a better name for the option are welcome. Maybe it should be something along the lines of...

> doesn't produce 1, but a Which is what should happen, right? Otherwise your strings get expanded into weird values if they happen to contain names of defined variables.

FWICT `exe_exists` is now called only from unit tests. If that is the case then let's just delete the whole thing. > I wonder if exe_exists simply exists because no...

The real problem here is predicting if changing the behaviour so that `@BOB` is not touched, will any downstream users break. Though I guess breaking a few is ok, but...

This is ugly as _sin_, but it now finally works on Linux at least (more specifically `run_project_tests.py --only common` does not produce any errors). There is no actual override ability...