Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

Tree [6fcadd] v2.0.10 /
History



File Date Author Commit
Applications 2008-11-17 Mathieu Malaterre Mathieu Malaterre [3716bd] ENH: final changes
CMake 2008-11-17 Mathieu Malaterre Mathieu Malaterre [3716bd] ENH: final changes
Examples 2008-11-17 Mathieu Malaterre Mathieu Malaterre [3716bd] ENH: final changes
Source 2008-12-05 Mathieu Malaterre Mathieu Malaterre [b9a198] ENH: backport merge -r 4825:4826 https://gdcm.s...
Testing 2008-11-17 Mathieu Malaterre Mathieu Malaterre [3716bd] ENH: final changes
Utilities 2008-12-02 Mathieu Malaterre Mathieu Malaterre [0d0ca1] BUG: fix
Wrapping 2008-11-17 Mathieu Malaterre Mathieu Malaterre [3716bd] ENH: final changes
debian 2008-12-05 Mathieu Malaterre Mathieu Malaterre [6fcadd] ENH: merge from trunk
AUTHORS 2008-11-17 Mathieu Malaterre Mathieu Malaterre [3716bd] ENH: final changes
CMakeLists.txt 2008-11-19 Mathieu Malaterre Mathieu Malaterre [2424e2] ENH: quick fix
CTestConfig.cmake 2008-05-14 Mathieu Malaterre Mathieu Malaterre [ff7bb3] ENH: dashboards have moved to cdash
Copyright.txt 2008-09-25 Mathieu Malaterre Mathieu Malaterre [940021] ENH: merging back 4051:4426 changed. svn merge ...
INSTALL.txt 2008-09-25 Mathieu Malaterre Mathieu Malaterre [940021] ENH: merging back 4051:4426 changed. svn merge ...
README.txt 2008-11-15 Mathieu Malaterre Mathieu Malaterre [f5dd33] ENH: svn merge -r 4427:4763 https://gdcm.svn.so...
TODO 2008-11-17 Mathieu Malaterre Mathieu Malaterre [3716bd] ENH: final changes

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/wiki/index.php/GDCM_Release_2.0
* http://gdcm.sourceforge.net/wiki/index.php/FAQ

And a page describing each tool can be found at:
* http://gdcm.sourceforge.net/wiki/index.php/Gdcmimg
* http://gdcm.sourceforge.net/wiki/index.php/Gdcmraw
* http://gdcm.sourceforge.net/wiki/index.php/Gdcmdump
* http://gdcm.sourceforge.net/wiki/index.php/Gdcmconv
* http://gdcm.sourceforge.net/wiki/index.php/Gdcmtar

Need VTK:
* http://gdcm.sourceforge.net/wiki/index.php/Gdcmviewer