Go to file
openkylin-cibot 15a5ed4a32 No change rebuild. 2024-05-22 07:21:51 +00:00
.github/workflows merge upstream 3.0.21 2024-02-29 18:13:02 +08:00
Applications Import Upstream version 3.0.22 2024-04-24 14:59:03 +08:00
CMake Import Upstream version 3.0.22 2024-04-24 14:59:03 +08:00
Examples Import Upstream version 3.0.22 2024-04-24 14:59:03 +08:00
Source Import Upstream version 3.0.22 2024-04-24 14:59:03 +08:00
Testing Import Upstream version 3.0.22 2024-04-24 14:59:03 +08:00
Utilities Import Upstream version 3.0.22 2024-04-24 14:59:03 +08:00
Wrapping merge upstream 3.0.21 2024-02-29 18:13:02 +08:00
debian No change rebuild. 2024-05-22 07:21:51 +00:00
.clang-format Import Upstream version 3.0.5 2022-05-14 03:28:55 +08:00
.clang-tidy Import Upstream version 3.0.22 2024-04-24 14:59:03 +08:00
.gitattributes merge upstream 3.0.21 2024-02-29 18:13:02 +08:00
.travis.yml merge upstream 3.0.21 2024-02-29 18:13:02 +08:00
AUTHORS merge upstream 3.0.21 2024-02-29 18:13:02 +08:00
CMakeLists.txt Import Upstream version 3.0.22 2024-04-24 14:59:03 +08:00
CTestConfig.cmake Import Upstream version 3.0.5 2022-05-14 03:28:55 +08:00
Copyright.txt Import Upstream version 3.0.5 2022-05-14 03:28:55 +08:00
INSTALL.txt Import Upstream version 3.0.5 2022-05-14 03:28:55 +08:00
PACKAGER Import Upstream version 3.0.5 2022-05-14 03:28:55 +08:00
README.Copyright.txt Import Upstream version 3.0.5 2022-05-14 03:28:55 +08:00
README.md Import Upstream version 3.0.5 2022-05-14 03:28:55 +08:00
appveyor.yml merge upstream 3.0.21 2024-02-29 18:13:02 +08:00

README.md

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:

In Particular:

And a page describing each tool can be found at:

Eg:

Need VTK: