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

[Rashindra Manniesing]

Dear Kent,

 

I completely understand your point of view, and  indeed for this particular
application, GDCM1 can be used as well (most likely, haven't looked that
closely, yet).

 

Within my environment I always prefer to have the latest versions of the
libs, thus it feels kind of awkward to spent time to make the program works
for older versions. And that is clearly not a very strong argument  from a
general/ITK point of view.

 

So, with the prospective that ITK - GDCM1 won't be replaced with 2 in the
near future, I will spent some time making dicomimport independent of
external packages, in the hope of course it will part of future versions of
ITK J (and as  my acknowledgment towards the ITK community)

 

Best regards, Rashindra.

 

From: kent williams [mailto:norman-k-williams at uiowa.edu] 
Sent: donderdag 5 november 2009 17:49
To: Rashindra Manniesing; ITK; insight-users at itk.org
Subject: Re: [Insight-developers] ITK and VS6 (and GDCM)

 

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/pipermail/insight-users/attachments/20091105/ac7194ca/attachment-0001.htm>