[Insight-developers] ITK and VS6 (and GDCM)

[kent williams]

As has been mentioned, there are reasons why gdcm 2 may never be the
Œnative¹ version of gdcm included with ITK.  As you¹ve discovered, it is
possible to build ITK using a Œsystem¹ GDCM 2. This is fine if you feel you
can¹t live without GDCM 2 facilities.

But, this discussion came about because of your Dicomimport tool, submitted
to the Insight Journal.  I haven¹t combed through the source exhaustively,
but I don¹t understand what GDCM 2 capabilities are necessary for this
application?  I would think that if you want Dicomimport to be part of
InsightApplications as a utilit, it would be worth spending the time to add
support for GDCM 1.x.   GDCM 2.0 has obvious advantages over 1.x, but I
don¹t think there¹s anything in 2.0 that can¹t be done in 1.x with a little
effort.

Dicomimport is a program we¹d very much like to use at Iowa  as part of our
toolset as our raison d¹etre is processing  a large volume of volumetric
imaging, including dicom files straight from the scanner.  But it would
require us to add GDCM to the list of packages that are prerequisite to
BRAINS, along with ITK, VTK, KWWidgets, VTKINRIA3D, FFTW, Tcl, Tk, etc.
Every time we add another package prerequisite it adds complexity and
brittleness to our build system, so we never do it lightly.


On 11/5/09 10:46 AM, "Rashindra Manniesing" <rashindra at gmail.com> wrote:

>  
> Dear all,
>  
> I heavily rely on the GDCM 2.0.x package for dicom-file handling, in ITK.
>  
> Unfortunately, ITK still ships with GDCM 1.x, apparently, because ITK still
> supports VS 6.0.
>  
> With the risk of repeating a previous discussion on the subject, but I think
> it is important enough, I was wondering: why still VS6, with VS10 already
> lying ahead? Shouldn't we all move forward?
>  
> Best regards,  Rashindra
>  
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.itk.org/mailman/private/insight-developers/attachments/20091105/1e11d5e7/attachment.htm>