官方安装DCMTK3.6.0的步骤:
详细中文安装步骤可以参考下面两篇:
1、 DCMTK3.6(MD支持库)安装说明
2、 DCMTK3.6.0 (MT支持库)安装 完整说明
BUILDING (Windows) ================== Starting with DCMTK 3.5.4, no project files for Visual Studio are provided anymore. Project files for all supported compilers can be generated with CMake. CMake is a cross-platform, open-source make system which can be used to control the software compilation process using simple configuration files. CMake can be obtained free of charge from http://www.cmake.org/. For configuring the support of external libraries in DCMTK on Windows platforms, the toolkit contains corresponding "CMakeLists.txt" files in all necessary directories. In detail, these "CMakeLists.txt" files will serve as an input to CMake which will generate new ".dsp" and ".dsw" files (or ".sln" for Visual Studio) for all of DCMTK's projects from these files, depending on a configuration which can be adjusted manually by the user. In order to be able to use CMake for configuration purposes in DCMTK, perform the following steps to install CMake on your machine: 1. Go to http://www.cmake.org/ to download the latest release version of CMake for Windows. With regard to a certain CMake version, note that CMake 2.4.8 or later can be used in conjunction with DCMTK. 2. Execute the file which was downloaded to install CMake on your machine. Follow all install instructions appropriately. In order to manually configure the support for the above mentioned external libraries (OpenSSL, zlib, libtiff, libpng and libxml2) through CMake, perform the following steps: 1. Go Start -> Programs -> CMake -> "CMake" or "CMake (cmake-gui)" to start the CMake utility through which the configuration can be done. 2. In the entry field "Where is the source code:" enter the directory in which the DCMTK source code resides, e.g. "C:\dcmtk-3.6.0". 3. In the entry field "Where to build the binaries:" enter the directory in which the libraries and binaries are to be built, e.g. "C:\dcmtk-bin". 4. In the combobox "Build for:" or "Specify the generator for this project:" select the corresponding development environment which shall be used to compile DCMTK. 5. Go "Configure". (CMake will look for a corresponding compiler, read in all of DCMTK's "CMakeLists.txt" files and perform some tests. The variables in the tabular area will be displayed in red. These variables can now be set in order to turn the support for any of the external libraries on or off). 6. Make the corresponding configurations in CMake's user interface. For example, in order to turn on libxml2 support, set the value of variable "DCMTK_WITH_XML" to "ON" and set the value of variable "WITH_LIBXMLINC" to the path where the include files and libraries of libxml2 can be found, e.g. "C:\libxml2-2.7.7". The support of all other external libraries can be turned on in a similar way: libpng support: set "DCMTK_WITH_PNG" to "ON" and set "WITH_LIBPNGINC" e.g. to "C:\libpng-1.4.2" libtiff support: set "DCMTK_WITH_TIFF" to "ON" and set "WITH_LIBTIFFINC" e.g. to "C:\tiff-3.9.2" OpenSSL support: set "DCMTK_WITH_OPENSSL" to "ON" and set "WITH_OPENSSLINC" e.g. to "C:\openssl-1.0.0" zlib support: set "DCMTK_WITH_ZLIB" to "ON" and set "WITH_ZLIBINC" e.g. to "C:\zlib-1.2.5" In order to turn the support of a certain external library off, set the value of the corresponding variable ("DCMTK_WITH_XML", "DCMTK_WITH_PNG", "DCMTK_WITH_TIFF", "DCMTK_WITH_OPENSSL", or "DCMTK_WITH_ZLIB") to "OFF". (Please note that the include files of all external libraries are always expected in a directory named "include" below the directory which is specified in "WITH_LIBXMLINC", "WITH_LIBPNGINC", "WITH_LIBTIFFINC", "WITH_OPENSSLINC", or "WITH_ZLIBINC"). (Please note also that the library files of all external libraries are always expected in directory named "lib" below the directory which is specified in "WITH_LIBXMLINC", "WITH_LIBPNGINC", "WITH_LIBTIFFINC", "WITH_OPENSSLINC", or "WITH_ZLIBINC". Moreover, note that the following filenames must be used for the corresponding lib files: libxml2: "iconv_d.lib" - debug version "iconv_o.lib" - release version (optimized) "libxml2_d.lib" - debug version "libxml2_o.lib" - release version (optimized) libpng: "libpng_d.lib" - debug version "libpng_o.lib" - release version (optimized) libtiff: "libtiff_d.lib" - debug version "libtiff_o.lib" - release version (optimized) openssl: "libeay32_d.lib" - debug version "libeay32_o.lib" - release version (optimized) "ssleay32_d.lib" - debug version "ssleay32_o.lib" - release version (optimized) zlib: "zlib_d.lib" - debug version "zlib_o.lib" - release version (optimized) The debug versions of all libraries must be compiled for the multithread debug version of the runtime (/MTd), the release version must be compiled for the non-debug multithread runtime (/MT). Precompiled versions of all libraries can be downloaded from http://dicom.offis.de/dcmtk). 7. Go "Configure" a second time. (CMake will adjust the configuration according to the displayed specifications). 8. Go "OK" or "Generate". (CMake will generate new project files in the corresponding directories. These files will be adjusted according to the displayed specifications, i.e. support for the external libraries will be turned on or off). Having performed these steps, the Microsoft Visual Studio IDE can be started, DCMTK's workspace file can be opened, and one or more of DCMTK's subprojects can be built. In case you want to build all libraries and applications, mark the "ALL_BUILD" subproject and build it. The "INSTALL" subproject installs the executables, libraries, include, support and documentation files (very similar to "make install-all" on Unix systems). Please note that other Windows compilers, e.g. Borland C++ Builder, are currently not actively supported. However, they may work. Known limitations of DCMTK on the Windows platform. 1. The dcmqrscp tool cannot spark multiple processes. Every association must be handled completely before a new association is possible. 2. On Windows 95, dcmqrscp always uses exclusive file locking (the LockFileEx API call is available on Windows NT only). This is no problem if only one single process exists. 3. Most applications will only work if the computer has configured TCP/IP, a network name and a TCP/IP address. If SLIP or PPP is used the applications can only work if a connection to a provider exists (since the internet addresses and names are given dynamically). 4. Visual C++ contains two different implementations of I/O streams which should never be mixed within one application because this may cause application errors that are hard to find. The old, now deprecated implementation uses the traditional cfront header filesetc. The new implementation uses etc. as defined in ANSI/ISO C++. DCMTK can be configured to use either of the two interfaces. This behaviour can be changed in "include/dcmtk/config/osconfig.h" in the build directory where the symbol USE_STD_CXX_INCLUDES is declared. NOTE: Previous releases of DCMTK (3.5.1 and older) used the old interface when compiled with Visual C++ 6.0. When updating software that uses DCMTK as a library, make sure that the use of the iostream library is consistent throughout the complete application!
参考文章:http://support.dcmtk.org/docs/file_install.html