2016-08-24 14:46 GMT+01:00 Guus Sliepen <[email protected]>:
> On Wed, Aug 24, 2016 at 02:37:52PM +0100, Ghislain Vaillant wrote:
>
> > > The problem seems to be an extra set of "../" in
> > > /usr/lib/cmake/glm/glmConfig.cmake
> > >
> > No, the problem is that the CMake config file should be installed in a
> > multiarch path, i.e.:
> >
> > /usr/lib/<multiarch-triplet>/cmake/glm/glmConfig.cmake
>
> No, glm is a header-only library and the -dev package is arch-all. So
> installing glmConfig.cmake in an architecture dependent path is
> nonsense.
>
>
Indeed.
But the upstream build system is using GNUInstallDirs to compute the targets
and config paths like this one:
set(GLM_INSTALL_CONFIGDIR "${CMAKE_INSTALL_LIBDIR}/cmake/glm")
And these are normally multiarch AFAIK. So these paths would have to be
manually overridden in d/rules.
> In the future, please add an appropriate autopkgtest for the -dev package
> > to detect packaging
> > issues like this one earlier.
>
> I'll see if I can add that.
>
> --
> Met vriendelijke groet / with kind regards,
> Guus Sliepen <[email protected]>
>
I would have offered to provide a patch, but I can't find a VCS link in
here:
https://packages.debian.org/source/sid/glm
Are Vcs-Browser and Vcs-Git properly set?
Ghis
