[Insight-developers] GDCM 2.x [was CMake Flag to make itk::Image behave like itk::OrientedImage]

[Hans Johnson]

All,

For those of us who do not have customers using VS6, but do have a great
need for many of the dicom processing features available in GDCM 2.0
(private field tag processing!), what is the recommended path?

Thanks,
Hans

-- 
Hans J. Johnson, Ph.D.
Hans-johnson at uiowa.edu

278 GH
The University of Iowa
Iowa City, IA 52241
(319) 353 8587


> From: Bill Lorensen <bill.lorensen at gmail.com>
> Date: Mon, 15 Sep 2008 11:49:02 -0400
> To: Stephen Aylward <Stephen.Aylward at kitware.com>
> Cc: ITK <insight-developers at itk.org>
> Subject: Re: [Insight-developers] GDCM 2.x [was CMake Flag to make itk::Image
> behave like itk::OrientedImage]
> 
> Unfortunately, Mathieu says that the new GDCM will not compile under
> VS6. I believe we still have customers that use VS6. There have been
> recent questions regarding VS6 on the users list.
> 
> Mathieu,
> 
> What sort of errors do you get with a VS6 compiler?
> 
> Bill
> 
> On Mon, Sep 15, 2008 at 11:44 AM, Stephen Aylward
> <Stephen.Aylward at kitware.com> wrote:
>> On Mon, Sep 15, 2008 at 11:06 AM, Karthik Krishnan
>> <karthik.krishnan at kitware.com> wrote:
>>> If I am not mistaken, I don't think the Backward compatibility policy
>>> applies to any of the third party software in Insight/Utilities.
>> 
>> Actually, we consider all API's published by ITK to be "public APIs of
>> ITK."    We debated how this applied to Utilities many years ago, and
>> the final agreement was that there should be every effort to maintain
>> the quality and backward-compatibility of the code and APIs in
>> Utilities as much as possible.   You can probably search the email
>> archives and find that discussion.
>> 
>>> 
>>>> Here is what I am planning to do : add support for the new GDCM 2.x
>>>> architecture via the use of ITK_USE_SYSTEM_GDCM. A compiler #ifdef
>>>> will determine the MAJOR version of GDCM and if GDCM 2.x is found, a
>>>> different implementation will be used,
>>> 
>>> Out of curiosity, is that more of a pain than upgrading the GDCM in
>>> ITK to 2.0.x ? If so, I wonder what the developers think about
>>> upgrading the GDCM in ITK, since DICOM handling is pretty fundamental
>>> for ITK.
>> 
>> I think we should upgrade.   If the API breaks backward compatibility,
>> then we need to acknowledge it, warn users, and try to mitigate the
>> negative effects.
>> 
>> The rough part happens is when someone has been compiling with
>> use-system-gdcm and that system gdcm is version X and now itk's
>> internal gdcm is moved to version X+1.    We may need to make changes
>> in ITK to allow either version to be used externally as well as
>> version X+1 internally.  Yuck...but an improved dicom reader is worth
>> it.
>> 
>> Stephen
>> 
>>> 
>>> Thanks
>>> --
>>> Karthik Krishnan
>>> R&D Engineer,
>>> Kitware Inc.
>>> Ph: 518 371 3971 x119
>>> Fax: 518 371 3971
>>> _______________________________________________
>>> Insight-developers mailing list
>>> Insight-developers at itk.org
>>> http://www.itk.org/mailman/listinfo/insight-developers
>>> 
>> 
>> 
>> 
>> --
>> Stephen R. Aylward, Ph.D.
>> Chief Medical Scientist
>> Kitware, Inc. - North Carolina Office
>> http://www.kitware.com
>> (518) 371-3971 x300
>> _______________________________________________
>> Insight-developers mailing list
>> Insight-developers at itk.org
>> http://www.itk.org/mailman/listinfo/insight-developers
>> 
> _______________________________________________
> Insight-developers mailing list
> Insight-developers at itk.org
> http://www.itk.org/mailman/listinfo/insight-developers



Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged.  If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited.  Please reply to the sender that you have received the message in error, then delete it.  Thank you.