+ need to
+ <UL>
+ <LI> <A HREF="GdcmDataCvs.html">retrieve gdcmData</A>
+ i.e. the set of Dicom image used in the test suite and
+ expand them in a directory refered as <TT>gdcmDATA</TT>.
+ </LI>
+ <LI> setup cmake <TT>GDCM_DATA_ROOT</TT> to <TT>gdcmDATA</TT>.
+ </LI>
+ </UL>
+ </LI>
+ <LI> <TT>CMAKE_BUILD_TYPE</TT> can be set up to <TT>Debug</TT>
+ if you plan to use your native debugger.
+ </LI>
+ <LI> <TT>CMAKE_CXX_FLAGS</TT> for cautious developpers should be
+ set to
+ <TT>-g -O0 -Wall -W -Wshadow -Wunused -Wno-system-headers -Wno-deprecated
+ -Woverloaded-virtual
+ </TT>
+ </LI>
+ </UL>
+</LI>
+<LI>
+ Hit <B><TT>c</TT></B> a couple times until they are no remaining "*"
+ (star character) preceeding the values of the gdcm variables.
+ <BR>
+ If you get warnings about
+ <TT>CMake forcing CMAKE_CXX_FLAGS</TT> (or other compiler variables)
+ simply ignore them and hit <B><TT>e</TT></B> to resume configuration.
+</LI>
+<LI>
+ Hit <B><TT>g</TT></B> in order to generate the makefiles (on Un*x)
+ or the workspace and project (on Win32).
+</LI>
+<LI>
+ Hit <B><TT>q</TT></B> to exit from <TT>ccmake</TT>.
+</LI>
+<LI> On Un*x launch <TT>make</TT>. On Win32 enter the VC++ gdcm.dsw
+ and lauch a <TT>build all</TT>.
+</LI>
+</UL>
+
+<!###################################>
+<H2>Installation</H2>
+This is an optional stage for developpers.
+<BR>
+On Un*x proceed with the install stage with <TT>make install</TT>.
+
+<!###################################>
+<H2>Running the test suite</H2>
+The impatient can run the full test suite with <TT>make test</TT>.
+<BR>
+For the test suite to be effective, you must have set
+<TT>BUILD_TESTING</TT> to <TT>ON</TT> when configuring <TT>ccmake</TT>.
+<UL>
+<LI>
+ <UL>
+ <LI> if you run the tests BEFORE installing then
+ positionate the environment variable <TT>GDCM_DICT_PATH</TT>
+ to <TT>gdcmSOURCES/Dicts</TT>
+ (e.g. <TT>export GDCM_DICT_PATH=$(gdcmSOURCES)/Dicts</TT>)
+ </LI>
+ <LI> if you run the tests AFTER installing then
+ positionate the environment variable <TT>GDCM_DICT_PATH</TT>
+ to <TT>gdcmINSTALL/share</TT>
+ (e.g. <TT>export GDCM_DICT_PATH=$(gdcmINSTALL)/Dicts</TT>)
+ </LI>
+ </UL>
+</LI>
+<LI>Assuming your current working directory is <TT>gdcmBINARY</TT>
+ the gdcm tests can be run in three different modes:
+ <OL>
+ <LI> Interactive access by number: run
+ <TT>./bin/gdcmTests</TT>
+ and select the number of the test you wish to run.
+ </LI>
+ <LI> Access to a test through it's name : pass the name of the
+ test as an argument to
+ <TT>./bin/gdcmTests</TT>
+ e.g.
+ <TT>./Test/gdcmTests TestAllEntryVerify</TT>.
+ </LI>
+ <LI> Launch the full test suite : (again we assume the
+ current working directory is <TT>gdcmBINARY</TT>)
+ run <B><TT>ctest</TT></B>. This is equivalent to <TT>make test</TT>.
+ <BR>
+ ctest supports some options (refer to the
+ <A HREF="http://www.cmake.org">CMake documentation</A>
+ for other options) :
+ <UL>
+ <LI> a verbose mode e.g. <TT>ctest -V</TT>
+ </LI>
+ <LI> argument filtering with regexp e.g. <TT>ctest -R print -V</TT>
+ runs the tests containing "print" in their name and
+ makes a verbose output.
+ </LI>
+ </UL>