Re: cmake and buildlink

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

Thomas Klausner <wiz%gatalith.at@localhost> wrote:
>On Mon, Oct 14, 2024 at 11:06:18PM +0100, Robert Swindells wrote:
>> I am trying to get wip/py-pyside-setup to build.
>> 
>> It generates some source files for bindings to Qt5 then tries to
>> compile those source files. This fails as the cmake scripts within
>> the package are not setup to look in the work/.buildlink directory
>> for headers.
>> 
>> Are there any other packages that do something similar that I can copy?
>
> From the build framework's/compiler's POV, it should look in
> /usr/pkg/include (etc.) for the headers like usual. pkgsrc's
> buildlink3 framework intercepts the compiler command line and rewrites
> it to look in ${WRKSRC}/.buildlink instead.
>
> So there should be no reason to tell anything in the build framework
> to look in ${WRKSRC}/.buildlink directly.

The package that I am trying to build contains a compiler-like tool that
is then used for the later stages of that package, there isn't a wrapper
around this tool to tell it to look in .buildlink and .x11-buildlink.

Have added a patch to a cmake script within the package to make the tool
look in .buildlink, my initial question was on whether there is a better
way to do this.

Tried building the package outside pkgsrc but cmake (from pkgsrc)
doesn't seem to be able to run pkgconfig to locate the required
dependencies. I'm guessing that cmake would normally add
-I/usr/X11R7/include to the compiler command line and everything would
work.

The build now gets a lot further but stops with a segv in Python.