[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Building python extensions with meson



Hello,

I maintain wreport[1], which is a simple C++ library with Python
bindings.

The package builds fine on bullseye and bookworm, but fails to build on
sid. On sid, meson tries to install the Python extension under
/usr/local instead of /usr.

I do not understand what has changed, nor how to fix it. I looked on
sources.debian.net[3] for other packages containing `python.get_install_dir(pure : false)
but I only found pycairo and pygobject, which however can also use
setup.py to build.

Or xraylib. xraylib doesn't build the python bindings in Debian, but if
I try to make it do that, as I'm supposed to, I get in the same
situation as wreport.

Did something break between bookworm and sid, in the interaction between
meson and Python?

Adding --buildsystem=pybuild to wreport's debian/rules didn't help, and
indeed, at least according to grep, pybuild doesn't seem to know about
meson.

This[3] meson issue has a lot of discussion, but I can't tell how much
of it is relevant.

Can anyone help me understand what is going on?


[1] https://tracker.debian.org/pkg/wreport
[2] https://codesearch.debian.net/search?q=python.get_install_dir
[3] https://github.com/mesonbuild/meson/issues/8739

Enrico

-- 
GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini <enrico@enricozini.org>

Attachment: signature.asc
Description: PGP signature


Reply to: