[Ctk-developers] problem compiling dcmtk

[Marco Nolden]

Hi Andras,

we had a long discussion about this a few months ago. We did not come to 
a final decision, but I think the most preferable way of integration 
would be to support the official DCMTK release at least on build level, 
e.g. disabling all functionality that depends on newer versions. This 
would allow people to use CTK even if they prefer to use an official 
DCMTK release or already are using DCMTK in their projects.

 From the MITK point of view and what I heard from our users it would be 
ok to use snapshot releases, as long as they are somehow "official", 
e.g. announced by OFFIS. I found 
http://dicom.offis.de/download/dcmtk/snapshot/ with a snapshot from 
February. @Michael: is this somehow "official", what are the criteria 
for releasing a snapshot?

Best,

Marco






On 03/06/2012 04:13 PM, Andras Lasso wrote:
> Hi guys,
>
> Just one more piece of information that may be relevant for this discussion:
> We are working on adding radiotherapy extensions to Slicer4
> (https://www.assembla.com/spaces/sparkit/wiki/SlicerRT) and due to the
> outdated DCMTK version in CTK (that doesn't contain RT objects) we have to
> work on a clone of CTK that uses a recent DCMTK. This also means that we
> cannot make the results of our work available to the whole Slicer community
> as standard extensions until CTK moves to a recent DCMTK version.
>
> So, for us upgrading to a more recent DCMTK in CTK would be very important.
> June would be OK, but the earlier the better. Waiting till Christmas would
> very much hinder our project.
>
> Thank you for considering this. Let me know if we can help with anything
> (testing, etc.).
> Andras
>
>
> -----Original Message-----
> From: ctk-developers-bounces at commontk.org
> [mailto:ctk-developers-bounces at commontk.org] On Behalf Of Marco Nolden
> Sent: 2012-March-06 9:51 AM
> To: Michael Onken
> Cc: OFFIS DICOM Team; ctk-developers at commontk.org
> Subject: Re: [Ctk-developers] problem compiling dcmtk
>
> On 02/29/2012 04:41 PM, Michael Onken wrote:
>> Hi Curzio,
>>
> [...]
>>
>> This problem has been fixed meanwhile in DCMTK (see commit [1]). You
>> might try the latest DCMTK code or apply a local patch.
>>
>> Best regards,
>> Michael
>>
>> [1]
>>
> http://git.dcmtk.org/web?p=dcmtk.git;a=commitdiff;h=dbadc0d8f3760f65504406c8
> b2cb8633f868a258
>>
>
> Hi Michael,
>
> for an (internal) clang compatibility test of MITK I also used DCMTK
> 3.6.0 with a cherry-pick of this commit. Since we want to support clang
> officially before the next DCMTK release I was wondering where to
> publish this version. Or do you think it would be possible to integrate
> a DCMTK 3.6.0 with dbadc0d8f3 applied in the official DCMTK repo? Or
> would you prefer that we put this somewhere else, maybe on
> github/commontk/DCMTK like Julien suggested?
>
> The commontk/DCMTK though is currently a bit outdated I'm afraid. IIRC
> it's based on DCMTK 3.5.4 with two commits by Steve and a few backports
> to fix compiler issues which are probably included in 3.6 anyway.
>
> Best,
>
> Marco
>
>
>
>
>
>


-- 
----------------------------------------------------------------------
Dipl.-Inform. Med. Marco Nolden
Deutsches Krebsforschungszentrum       (German Cancer Research Center)
Div. Medical & Biological Informatics          Tel: (+49) 6221-42 2325
Im Neuenheimer Feld 280                        Fax: (+49) 6221-42 2345
D-69120 Heidelberg                             eMail: M.Nolden at dkfz.de