X-Git-Url: https://git.creatis.insa-lyon.fr/pubgit/?a=blobdiff_plain;f=README;h=f4f531397c4cc6d635c5601dd90f4d40ae8df3e2;hb=HEAD;hp=cc409ad1c809f0fe82760efa425c822838e71707;hpb=d4f7a5d74be3a4a332380d24631f3d0d96f98f5f;p=gdcm.git diff --git a/README b/README index cc409ad1..f4f53139 100644 --- a/README +++ b/README @@ -1,14 +1,28 @@ -MANIFEST: - * gdcmlib is a library dedicated to reading and writing dicom files. - * LGPL for the license - * lightweigth as opposed to CTN or DCMTK which come bundled which try - to implement the full DICOM standard (networking...). gdcmlib concentrates - on reading and writing files (if you want DICOMNET, forget it). - * Formats: this lib should be able to read ACR-NEMA v1 and v2, Dicom v3 (as - stated in part10). [cf dcmtk/dcmdata/docs/datadict.txt] - * Targeted plateforms: Un*xes and Win32/VC++6.0 - -REQUIREMENTS: - * a C++ compiler with the and STL containers. - * the python wrappers require Swig version >= 1.3.17 for handling member - overloading, shadow classes and static methods. +For a general introduction/features/limitations/requirement please +refer to http://www.creatis.insa-lyon.fr/Public/Gdcm + +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, VS6/7/8 Project, XCode 1.5... +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 aby 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 to 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 cvs copy and compile safely knowing that there are very few chances +that something won't work. Cheers ! + + +(*) http://www.cmake.org for more information