Date: Fri, 29 Mar 2024 10:48:18 +0000 (UTC) Message-ID: <1811330504.47.1711709298266@10566d94d4ce> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_46_64210315.1711709298266" ------=_Part_46_64210315.1711709298266 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
In order to build all components of the dcm4che2 toolkit you will need t= o download and install:
In addition, you will have to download the dcm4che2 source code from the= dcm4che project at SourceForge, or get it directly from SVN:
svn co https://dcm4che.svn.sourceforge.net/svnroot/dcm4che/dcm4che2/tr= unk dcm4che2
There are two pieces to building dcm4che2: building the DICOM dictionary= , and building the software itself. Building the dictionary is purely o= ptional, as the standard dictionary is included in the application alr= eady. However, if you want to customize the dictionary, or add items to it = that have not yet been included in the standard yet, then knowing how to bu= ild the dictionary is a good thing.
Building dcm4che2 is relatively easy, as Maven manages the dependencies = for you. Assuming that you have the Maven executable scripts on your path..= . Simply navigate to the root of the dcm4che2 source directory structure, a= nd type:
mvn install assembly:assembly
or (to avoid test failure in DicomImageWriterTest in versions prior to <= code>2.0.20)
mvn install assembly:assembly -P nojiio
This will build distributions of the dcm4che2 toolkit. That's it! You ma=
y then find the zip distribution file in the target directory and copy/extr=
act it to wherever you wish.
/dcm4che2/dcm4che2-core
is the project that contains the ba=
se dictionary files and the build script that generates the serialized file=
which gets included in the distribution. The DICOM standard is contained i=
n an OpenOffice format. These documents are parsed using the appropriate DT=
D, and transformed (with XSL) into XML documents. These XML documents are t=
hen used as input to another XSL process which will generate org.dcm4=
che2.data.Tag.java
, org.dcm4che2.data.UID.java
, d=
ictionary.xml
, and uids.xml
. The two Java files are com=
piled later as part of the dcm4che-core build process. The two XML files ar=
e used to generate serialized data dictionaries which are accessed at run t=
ime. These data dictionaries are ElementDictionary.ser
, =
UIDDictionary.ser
, and VRMap.ser
.
Currently the movement of the generated Java and XML files over to the <= code>/dcm4che2/dcm4che-core directory structure is manual, as well a= s the generation of the serialized data dictionaries.
Within this directory, you'll see the following structure:
dcm4che2-core-dict | ----src | ----main | ----dtd | ----sxw | ----xml | ----xsl
The main
directory contains the content subdirectories and =
the Ant build script. The content subdirectories can be described as follow=
s:
.mod
, or .dtd
=
extensions.elements.xml
and =
uids.xml
files reference these generated XML files. There also=
exists a private-uids.xml
file which contains UIDs which are =
mainly used by dcm4chee and other applications to initiate custom DICOM beh=
avior.dictionary.xml
, uids.xml
), and XML documents into Java classes (org.dcm4che2.data.Tag.java=
code>, org.dcm4che2.data.UID.java
).