Hi Mathieu,
Clearly, there is a bug.
On February 8, 2014 03:35:58 PM Mathieu Malaterre wrote:
> Your point is correct, importing *solely* ITK 4.0 does work. However
> what does not work is clearly indicated at
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728121#10
>
correct, importing *solely* ITK 4.0 does work. However
what does not work is clearly indicated at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728121#10
This is a ~4 lines demonstration which makes the package unusable for
a lot of us.
As explained in ยง4.13:
https://www.debian.org/doc/debian
For reference here is the error message produced from the small
example at #728121#10
...
CMake Error at /usr/lib/cmake/ITK-4.5/ITKTargets.cmake:34 (message):
Some (but not all) targets in this export set were already defined.
Targets Defined:
gdcmjpeg8;gdcmjpeg12;gdcmjpeg16;gdcmCommon;gdcm
On Wed, Jan 29, 2014 at 11:02:35AM +0100, Mathieu Malaterre wrote:
> Control: severity 728121 grave
>
> Marking as grave since render the package unusable.
How does this render the package unusable? As one counter-example,
the package 'elastix' builds fine using the ITK -dev package.
-Steve
s
Control: severity 728121 grave
Marking as grave since render the package unusable.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hi all,
The following CMakeLists.txt fails, cause gdcm targets are defined twice.
Adding gdcm into the dependency would solve this blocking issue!
Thanks
Arnaud
---
project( foo )
cmake_minimum_required( VERSION 2.6 )
find_package( GDCM REQUIRED )
include( ${GDCM_USE_FILE} )
find_package( IT
Package: insighttoolkit4
It would be nice (isn't it a requirement?) to have insighttoolkit4 use
system installed GDCM, instead of the old copy (GDCM 2.0.16).
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.
7 matches
Mail list logo