There is a much longer list of features in GDCM2 that aren't in GDCM 1.x shipped with ITK, not to mention, its cleaner, easier to use and growing, (thanks to Mathieu), so much so, that for a while now I haven't used the GDCM shipped with ITK.<br>
<br>The point is : We should have a nightly dashboard at Kitware, that builds with system gdcm, just to be safe, on each platfom. Do you know if we have one already. I don't see it on the ITK dashboard. We would be grateful for any contributions.<br>
<br>Thanks<br>--<br>karthik<br><br><div class="gmail_quote">On Thu, Nov 5, 2009 at 11:49 AM, kent williams <span dir="ltr"><<a href="mailto:norman-k-williams@uiowa.edu">norman-k-williams@uiowa.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size: 11pt;">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.<br>
<br>
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.<br>
<br>
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.<div>
<div></div><div class="h5"><br>
<br>
<br>
On 11/5/09 10:46 AM, "Rashindra Manniesing" <<a href="http://rashindra@gmail.com" target="_blank">rashindra@gmail.com</a>> wrote:<br>
<br>
</div></div></span></font><div><div></div><div class="h5"><blockquote><font size="2"><font face="Consolas, Courier New, Courier"><span style="font-size: 10pt;"> <br>
Dear all,<br>
<br>
I heavily rely on the GDCM 2.0.x package for dicom-file handling, in ITK.<br>
<br>
Unfortunately, ITK still ships with GDCM 1.x, apparently, because ITK still supports VS 6.0.<br>
<br>
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?<br>
<br>
Best regards, Rashindra<br>
</span></font></font><font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size: 11pt;"> <br>
<br>
</span></font></blockquote>
</div></div></div>
<br>_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at<br>
<a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Kitware offers ITK Training Courses, for more information visit:<br>
<a href="http://kitware.com/products/protraining.html" target="_blank">http://kitware.com/products/protraining.html</a><br>
<br>
Please keep messages on-topic and check the ITK FAQ at:<br>
<a href="http://www.itk.org/Wiki/ITK_FAQ" target="_blank">http://www.itk.org/Wiki/ITK_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.itk.org/mailman/listinfo/insight-developers" target="_blank">http://www.itk.org/mailman/listinfo/insight-developers</a><br>
<br></blockquote></div><br><br clear="all"><br><br>