C++ C CMake HTML XSLT Python Other
Latest commit 4b2b710 Jul 26, 2017 @malaterre Merge branch 'release'
Permalink
Failed to load latest commit information.
Applications Fix a typo in the code Jul 20, 2017
CMake Merge branch 'release' Apr 27, 2017
Examples Really remove from compilation Jul 26, 2017
Source Merge branch 'release' Jul 26, 2017
Testing Do not run on MITRA_CORNELL for now Jul 20, 2017
Utilities Merge branch 'release' Jul 20, 2017
Wrapping Issue: gdcm 2.8.1 with Python Jul 17, 2017
.clang-format add clang format file Oct 8, 2015
.gitattributes prefer our version Nov 5, 2015
.gitignore Backport from master onto release branch Jun 22, 2011
.gitmodules Use new URL for gdcmData submodule Dec 17, 2012
.travis.yml
AUTHORS Updated some comments Jan 19, 2016
CMakeLists.txt Start 2.9.x devel Jun 29, 2017
CTestConfig.cmake Update URLs as per indications on cdash. Jul 18, 2014
Copyright.txt Updated some comments Jan 19, 2016
INSTALL.txt
PACKAGER Implementation of strict scanner Feb 25, 2015
README.Copyright.txt remove more trailing whitespace... Aug 25, 2010
README.txt Updated some comments Jan 19, 2016
TODO add TODO Oct 20, 2016
appveyor.yml Update appveyor Jun 29, 2017

README.txt

This is the source code of GDCM. It is available from sf.net website.
Official GIT repository is at:

  https://sourceforge.net/p/gdcm/gdcm/

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,
VS8/9/10 Solution, Xcode projects, etc.
3. Automatic nightly testing, one of the most important things
for a robust library/software development process. GDCM development 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 sent to
the dashboard located at:

  https://open.cdash.org/index.php?project=GDCM

A continuous dashboard also makes sure that any commit did not introduce
any error on another platform, a warning or a broken test...

Therefore you should be able to use GDCM from the bleeding edge without
knowing too much about what is going on. All you need to do is have a look
at the GDCM dashboard, and if your platform is 'green' then you can
update your git copy and compile safely knowing that there is very little chance
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://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/End_User_Applications

Eg:
* http://gdcm.sourceforge.net/wiki/index.php/Gdcminfo

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