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.

>
> Please check that
> - the wanted headers are there
> - the proper -I/usr/pkg/ flag is on the compiler command line
> - the proper compiler is used and the command is rewritten (see work/.work.log)

The error I get is because one of the qt5 headers can't find gl.h.

  /usr/pkg/qt5/include/QtGui/qopengl.h:141:13: fatal: 'GL/gl.h' file not found

The package uses clang as a library to parse the headers and (I'm
guessing) to derive C++ decorated symbols from them.