Excellent. It all makes sens. <div>Thanks for clarifying</div><div>Jc<br><br><div class="gmail_quote">On Tue, May 29, 2012 at 2:37 PM, Williams, Norman K <span dir="ltr"><<a href="mailto:norman-k-williams@uiowa.edu" target="_blank">norman-k-williams@uiowa.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The usual method of doing things would be<br>
<br>
IF(ITK_USE_SYSTEM_DCMTK)<br>
find_package(DCMTK REQUIRED)<br>
# yadda yadda.<br>
ENDIF()<br>
<br>
This would fail if DCMTK_DIR is not defined -- assuming of course DCMTK<br>
isn't installed in the standard paths.<br>
--<br>
Kent Williams <a href="mailto:norman-k-williams@uiowa.edu">norman-k-williams@uiowa.edu</a><br>
<br>
<br>
<br>
<br>
<br>
<br>
On 5/29/12 1:34 PM, "Jean-Christophe Fillion-Robin"<br>
<div class="HOEnZb"><div class="h5"><<a href="mailto:jchris.fillionr@kitware.com">jchris.fillionr@kitware.com</a>> wrote:<br>
<br>
><br>
>On Tue, May 29, 2012 at 11:55 AM, Williams, Norman K<br>
><<a href="mailto:norman-k-williams@uiowa.edu">norman-k-williams@uiowa.edu</a>> wrote:<br>
><br>
><br>
>Jean-Christophe, it seems like what you're saying is that you wish<br>
>DCMTK_DIR, if defined, to in essence, force ITK_USE_SYSTEM_DCMTK. That's<br>
>fine, and looking how other external packages are dealt with -- FFTW being<br>
>the prime example -- that's how it would work.<br>
><br>
><br>
><br>
>If passing both -DITK_USE_SYSTEM_DCMTK:BOOL=ON and<br>
>-DDCMTK_DIR:PATH=/path/to/my/dcmtk when configuring ITK works as<br>
>expected, I guess that should be enough from Slicer perspective.<br>
><br>
>Thanks<br>
>Jc<br>
><br>
><br>
><br>
><br>
>Bill, I think that the goal, as indicated by Terry Yu, is that GDCM will<br>
>be deprecated, so the DCMTK reader will be the one true way to deal with<br>
>DICOM. This could be a problem for programs that have used GDCMImageIO<br>
>explicitly -- or used GDCM calls directly, but I think most people were<br>
>cured of that tendency when ITK went from GDCM1 to GDCM2, which broke<br>
>anything that used GDCM in a non-trivial fashion.<br>
><br>
>I think I see my way clear to make DCMTK work as well -- or probably<br>
>better -- than GDCM as a DICOM reader. I need to focus on that and<br>
>produce a Gerrit patch. There are a ton of peripheral issues around<br>
>DICOM reading that will take longer to iron out.<br>
><br>
>The fact of the matter is that DICOM is squirrelly enough to make it<br>
>impossible to use transparently with the existing ImageIO framework. For<br>
>one thing, the ImageFileReader/Writer really don't want to deal with<br>
>directories as image paths, so any program who wants to use ITK for Image<br>
>IO has to have infrastructure around ImageIO to sniff for the DICOM case<br>
>and do it differently than every other file format.<br>
><br>
>Plus DICOM is potentially quite a lot more than just files in a file<br>
>system, and ITK has never dealt with the rest of DICOM at all. Slicer4<br>
>has some support for network DICOM stuff, but they're using DCMTK directly<br>
>to handle that case.<br>
><br>
>On 5/29/12 10:28 AM, "Bill Lorensen" <<a href="mailto:bill.lorensen@gmail.com">bill.lorensen@gmail.com</a>> wrote:<br>
><br>
>>If you treat dcmtk as we treat vtk then you will not need a<br>
>>ITK_USE_SYSTEM_DCMTK.<br>
><br>
><br>
><br>
><br>
>________________________________<br>
>Notice: This UI Health Care e-mail (including attachments) is covered by<br>
>the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is<br>
>confidential and may be legally privileged. If you are not the intended<br>
>recipient, you are hereby notified that any retention, dissemination,<br>
>distribution, or copying of this communication is strictly prohibited.<br>
>Please reply to the sender that you have received the message in error,<br>
>then delete it. Thank you.<br>
><br>
><br>
>________________________________<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
>--<br>
><a href="tel:%2B1%20919%20869%208849" value="+19198698849">+1 919 869 8849</a><br>
><br>
<br>
<br>
<br>
________________________________<br>
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.<br>
________________________________<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>+1 919 869 8849<br><br>
</div>