[Debian-med-packaging] Bug#826048: Faulty CMake file impairs compiling against GDCM

[Mathieu Malaterre]

On Mon, Oct 17, 2016 at 3:19 PM, Carnë Draug <carandraug at octave.org> wrote:
> On 17 October 2016 at 07:40, Mathieu Malaterre <malat at debian.org> wrote:
>> Control: tags -1 moreinfo
>>
>> On Fri, Oct 14, 2016 at 5:29 PM, Carne Draug <carandraug at octave.org> wrote:
>>> Package: libgdcm2-dev
>>> Version: 2.6.6-1
>>> Followup-For: Bug #826048
>>>
>>> I'm not 100% sure if this is the same issue I'm having but I think
>>> so, so I' commenting here instead of opening a new one.
>>>
>>> The following was working fine in Debian Wheezy and returned the
>>> expected lib flags:
>>>
>>>     cmake --find-package \
>>>       -DNAME=GDCM \
>>>       -DCOMPILER_ID=GNU \
>>>       -DLANGUAGE=CXX \
>>>       -DMODE=LINK
>>
>> Does it work if you change into -DMODE=COMPILE ?
>
> Yes. Getting the compile flags works fine:
>
> $ cmake --find-package \
>         -DNAME=GDCM \
>         -DCOMPILER_ID=GNU \
>         -DLANGUAGE=CXX \
>         -DMODE=COMPILE
> -I/usr/include/gdcm-2.6
>
> $ cmake --find-package \
>         -DNAME=GDCM \
>         -DCOMPILER_ID=GNU \
>         -DLANGUAGE=CXX \
>         -DMODE=LINK
>
>
> The last command, -DMODE=LINK, simply returns an empty line.

Well it is in fact returning an empty string, so I would not consider
this a bug. As far as I understand the link line for GDCM should not
add anything. In the past (previous cmake version) it used to return
"-rdynamic". That does not seems required anymore.

GDCM libs are installed in the default path, so your linker should be
able to find them without tweaking the link line.

-M