-- GDCM_VTK When this option is on VTK_DIR might require manual
configuration
-- GDCM_WRAP_PYTHON
+ -- CMAKE_CXX_FLAGS (when working with gcc of course) should be set to
+ -g -O0 -Wall -W -Wshadow -Wunused-variable -Wunused-parameter
+ -Wunused-function -Wunused -Wno-system-headers -Wno-deprecated
+ -Woverloaded-virtual
+ (this is to avoid spurious problems with overloading)
* Configure cmake: hit c
* Generate the makefiles (or dsw): hit g
- Compile gdcm
typedef Header* HeaderPointer;
HeaderPointer MyHeaderPointer;
- One notorious counter example for non using C style inclusion concerns
- exact-width intergers (since there seem to be no equivalent for C++).
+ exact-width integers (since there seem to be no equivalent for C++).
When using exact-width integers use the typedef names defined by
the Basic ISO C99: 7.18 Integer types i.e.
int8_t int16_t int32_t int64_t (signed integers)
and
uint8_t uint16_t uint32_t uint64_t (unsigned integers).
+ Conversion table is then:
+ unsigned char -> uint8_t;
+ unsigned short -> uint16_t;
+ unsigned int -> uint32_t;
+ unsigned long -> uint32_t;
+ unsigned long long -> uint64_t;
+ (signed) char -> int8_t;
+ short -> int16_t;
+ int -> int32_t;
+ long -> int32_t;
+ long long -> int64_t;
Hence do not use declarations like "unsigned int".
With g++, accessing those typedef is achieved by the following
#include <stdint.h>
* you can start a single test through ctest with
ctest -R FailingTestName -V >& log
------------------------------------------------
+Compiler flags policy:
+ When working with gcc please use the flags specified in DEVELOPPER file
+ (in order to avoid difficult overloading problems).
+------------------------------------------------