Re: freecad

[Thomas Klausner <wiz%gatalith.at@localhost>]

On Thu, Mar 06, 2025 at 01:43:53PM +0000, Robert Swindells wrote:
> Some documentation on how Python packages are supposed to interact with
> buildlink would be useful, same for cmake.

If header files are in a non-standard location, you must tell
buildlink3 about it, otherwise they won't be linked, see e.g.:

BUILDLINK_INCDIRS.py-game_sdl2+=        ${PYINC}/pygame_sdl2

If there pkg-config-equivalent scripts are versioned, you might want
to un-version seem, see e.g.

pre-configure: py-pybind11-preconfigure
.PHONY: py-pybind11-preconfigure
py-pybind11-preconfigure:
        ${LN} -sf ${PREFIX}/bin/pybind11-config-${PYVERSSUFFIX} ${BUILDLINK_DIR}/bin/pybind11-config

I can't think of anything in particular for cmake.

> The cmake configuration part of py-pyside-setup looks for optional
> modules, numpy is one of those but it is failing to find several Qt5
> ones.

Make sure you have the latest pkgsrc - cmake was made to be more
strict in only finding buildlinked packages, and some packages needed
fixes for that, especially qt ones.

> There is also the problem that this stack of packages will only build
> with PYTHON_VERSION_DEFAULT=311 as py-boost-cmake doesn't pass
> PYTHON_PACKAGE down to things that it builds such as numpy.

py-boost-cmake looks wrong. Either it is Python-version-independent,
like it purports to be, then it shouldn't need to pull in (the
versioned) py-numpy, or it's not, then it should be properly
versioned.

I'm not sure why we're talking about it though, py-pyside-setup
doesn't pull it in?
 Thomas