Re: freecad

[Robert Swindells <rjs%fdy2.co.uk@localhost>]

Greg Troxel <gdt%lexort.com@localhost> wrote:
>mlh%goathill.org@localhost (MLH) writes:
>> So how do we force that with py-pyside-setup ?
>
> Generally:
>
>  file a bug upstream
>
>  patch it to search correctly.  numpy-config is very strange, with
>  --cflags but not --libs (never mind that -I is a cppflag, not a
>  cflag), and a pkgconfig file in an odd place (but multiversion python
>  so I see why).
>
>  patch it to check the possible directories for the numpy header and
>  use the one that's there.  Not really correct vs following
>  numpy-config/pkgconfig but not too bad.
>
>  patch it to work within pkgsrc.  We know what numpy version we have
>  and where it puts things.  Just remove all the conditionals and use
>  that.

Some documentation on how Python packages are supposed to interact with
buildlink would be useful, same 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.

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.