Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

Tree [1cd3f3] v2.0.14 /
History



File Date Author Commit
Applications 2009-11-11 Mathieu Malaterre Mathieu Malaterre [6ce798]
CMake 2009-11-11 Mathieu Malaterre Mathieu Malaterre [6ce798]
Examples 2009-11-12 Mathieu Malaterre Mathieu Malaterre [2460ea] svn merge --accept=postpone -r 6232:6244 https:...
Source 2009-11-12 Mathieu Malaterre Mathieu Malaterre [2460ea] svn merge --accept=postpone -r 6232:6244 https:...
Testing 2009-11-12 Mathieu Malaterre Mathieu Malaterre [2460ea] svn merge --accept=postpone -r 6232:6244 https:...
Utilities 2009-11-12 Mathieu Malaterre Mathieu Malaterre [2460ea] svn merge --accept=postpone -r 6232:6244 https:...
Wrapping 2009-11-12 Mathieu Malaterre Mathieu Malaterre [1cd3f3] revert
debian 2009-05-19 Mathieu Malaterre Mathieu Malaterre [b97d26] ENH: prepare merge:
AUTHORS 2009-10-24 Mathieu Malaterre Mathieu Malaterre [422cea] backport from trunk. svn merge --accept=postpon...
CMakeLists.txt 2009-11-11 Mathieu Malaterre Mathieu Malaterre [6ce798]
CTestConfig.cmake 2008-05-14 Mathieu Malaterre Mathieu Malaterre [ff7bb3] ENH: dashboards have moved to cdash
Copyright.txt 2009-05-19 Mathieu Malaterre Mathieu Malaterre [b97d26] ENH: prepare merge:
INSTALL.txt 2009-11-11 Mathieu Malaterre Mathieu Malaterre [6ce798]
PACKAGER 2009-11-11 Mathieu Malaterre Mathieu Malaterre [6ce798]
README.Copyright.txt 2009-05-19 Mathieu Malaterre Mathieu Malaterre [b97d26] ENH: prepare merge:
README.txt 2009-05-19 Mathieu Malaterre Mathieu Malaterre [b97d26] ENH: prepare merge:
TODO 2009-10-24 Mathieu Malaterre Mathieu Malaterre [422cea] backport from trunk. svn merge --accept=postpon...

Read Me

For a general introduction/features/limitations/requirement please
refer to http://gdcm.sourceforge.net/

Just a quick note on the build process of GDCM. GDCM build process
make use of the cmake software(*). This allow us:
1. To get rid of the autoconf/autotools insanity
2. Transparently generate Unix Makefiles, NMake Makefiles, 
Borland Makefiles, VS7/8/9 Project, XCode 1.5/2.1
3. Automatic nightly testing, one of the most important thing
for a robust library/software devlpt process. GDCM devpt is develop
based on the XP definition, and to preserve backward compatibility 
make sure that code is working from one release to another: each night
we configure, we build and we test GDCM. The result are then send to 
the dashboard located at:

   http://public.kitware.com/dashboard.php?name=gdcm

A continuous dashboard make also sure that any commit did not introduce
any error on another plateform, a warning or broke a test...

Therefore you should be able to use GDCM from the bleeding edge without
knowing too much on what is going on. All you need to do is have a look
at the GDCM dashboard, and if your plateform is 'green' then you can 
update your svn copy and compile safely knowing that there are very few chances
that something won't work. Cheers !


(*) http://www.cmake.org for more information

For more help you can go online in the GDCM Wiki:
* http://gdcm.sourceforge.net/

In Particular:
* http://apps.sourceforge.net/mediawiki/gdcm/index.php?title=GDCM_Release_2.0
* http://apps.sourceforge.net/mediawiki/gdcm/index.php?title=FAQ

And a page describing each tool can be found at:
* http://apps.sourceforge.net/mediawiki/gdcm/index.php?title=End_User_Applications

Eg:
* http://apps.sourceforge.net/mediawiki/gdcm/index.php?title=Gdcminfo

Need VTK:
* http://apps.sourceforge.net/mediawiki/gdcm/index.php?title=Gdcmviewer