poppler @23.11.0_0: Wrong dynamic library paths in typelib file

[FlyingSamson]

Currently the typelib file created by the poppler port /opt/local/lib/girepository-1.0/Poppler-0.18.typelib contains a dynamic library path that is relative to the build directory:

$> strings /opt/local/lib/girepository-1.0/Poppler-0.18.typelib | grep lib
/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_graphics_poppler/poppler/work/build/libpoppler-glib.8.dylib,/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_graphics_poppler/poppler/work/build/libpoppler.133.dylib

Correctly this should yield

/opt/local/lib/libpoppler-glib.8,/opt/local/lib/libpoppler.133

As a result when using poppler through gobject introspection, for instance, in python, fails because it cannot find the library file specified in the typelib file.

A patch for this can be found in this commit and the corresponding ​pull request.

[ryandesign (Ryan Carsten Schmidt)]

Upstream bug report URL for this problem?

[FlyingSamson]

A related upstream bug report would be ​this one. However, the patch proposed there is already included in patch-glib_CMakeFiles.txt-fix-include-ordering.diff of the poppler port. The patch propsed by myself is also done by the webkit2-gtk port in patch-webkit2gtk-specify-installed-dylibs.diff by the way.

But now that you mentioned it, it might make sense to leave a comment there that we are facing a similar issue with MacPorts, which is not fixed by the proposed patch.