PBTWiki - User contributions [en]

Software/Geant4/Installation

2016-06-05T21:08:24Z

LukasKikuchi: /* Geant4 Installation */

== Installation Of Geant4 And Supporting Packages ==

The [http://geant4.web.cern.ch/geant4/UserDocumentation/UsersGuides/InstallationGuide/html/index.html CERN Geant4 Installation Guide] provides extensive instructions on installing Geant4.
This provides an overview of the installation procedure, as well as a list of prerequisites and additional software that need to be installed alongside Geant4.

In addition, information is given on the installation procedure for this additional software and the location the software is installed on the [[Software/Geant4/UCL HEP Cluster|UCL HEP Linux Cluster]].

The <code>environment</code> described here is the combination of files, folders, settings and user interface that allow users to make use of <code>Geant4</code> and related software packages for particle beam therapy simulations.

Accessing the environment requires the following:
* Access to the filesystem and required folders.
* Terminal access to run simulations.
* A visualisation engine such as OpenGL on X (''optional'').
* Setting environment variables to point to installed software and scripts.

The order of installation is important, as some packages depend on having the other packages first.
In some cases, installations will be successful if carried out in the wrong order, but some features will be disabled that should be enabled.
The order of packages described below is the order in which these packages were installed into the PBT environment.

== Required Software ==

The list of required software is split into 2 categories:

* [[#Prerequisites|Prerequisites]] are those components that are required in order for some part of <code>Geant4</code> or the resulting simulation visualisations to function correctly;
* [[#Add Ons|Add Ons]] are optional pieces of software — normally visualisation software — that are installed on the [[Software/Geant4/UCL HEP Cluster|UCL HEP Linux Cluster]].

See the individually linked pages for information on building each of the components that do not ship by default.

=== Prerequisites ===

The [http://geant4.web.cern.ch/geant4/UserDocumentation/UsersGuides/InstallationGuide/html/index.html CERN Geant4 Installation Guide] provides extensive information on
[http://geant4.web.cern.ch/geant4/UserDocumentation/UsersGuides/InstallationGuide/html/ch01s02.html software that must be installed to compile Geant4 itself] and software required in order to
[http://geant4.web.cern.ch/geant4/UserDocumentation/UsersGuides/InstallationGuide/html/ch01s03.html compile optional components of Geant4].

These are:

* A C++11 compatible compiler: on Linux, this is [https://gcc.gnu.org <code>GCC</code>: the GNU Compiler Collection] which is installed by default.
* [[/CMake|<code>CMake</code>]] required for building the various <code>Geant4</code> simulations through <code>cmake</code> files.
* The [[/CLHEP|<code>CLHEP</code> Class Library]] that provides a range of foundation and utility classes needed for <code>Geant4</code> simulations.

* [https://www.opengl.org <code>OpenGL</code> headers and libraries] to provide support for <code>OpenGL</code> graphics (graphics card specific; installed by default on most Operating Systems).
* [https://en.wikipedia.org/wiki/X_Window_System <code>X11</code>] headers and libraries to provide support for the <code>X</code>-Window system (installed by default on <nowiki>*</nowiki>nix systems
* [[/Qt|<code>Qt4</code> or <code>Qt5</code> headers and libraries]] to provide support for the Qt user interface and visualisation.
* [[/Xerces-C|<code>Xerces-C++</code> headers and libraries]] compiled against the C++11 standard to provide support for GDML geometry descriptions.
* [http://www.opengroup.org/openmotif <code>Motif</code>] and X11 headers and libraries to provide support for the Motif user interface and visualisation (installed by default on Linux)
* [[/Coin3D|<code>Coin3D</code>]] for Open Inventor visualisation (<code>Coin3D</code> is a free implementation of Open Inventor). This requires the following libraries to be installed:
** The [[/Coin3D#simage|<code>simage</code>]] library with image format loaders and front-ends to common import libraries. <code>simage</code> is meant for use with applications which read image files as textures. '''<code>simage</code> must be installed before <code>Coin3D</code>'''.
** The [[/Coin3D#SoXt|<code>SoXt</code>]] open source InventorXt library, which is a GUI binding for using Open Inventor with Xt/Motif. <code>SoXt</code> must be installed after <code>Coin3D</code>.
** [[/Coin3D#SoQt|<code>SoQt</code>]] open source <code>Qt</code> GUI component toolkit library for <code>Coin3D</code>. <code>SoQt</code> must be installed after <code>Coin3D</code>.

=== Add Ons ===

The [http://geant4.web.cern.ch/geant4/UserDocumentation/UsersGuides/InstallationGuide/html/index.html CERN Geant4 Installation Guide] provides a range of
[http://geant4.web.cern.ch/geant4/UserDocumentation/UsersGuides/InstallationGuide/html/ch01s04.html software suggested for use with <code>Geant4</code>].
While none of these need to be installed for <code>Geant4</code> to compile and run, they are useful for visualising the resulting simulations.

The following subset is installed on the [[Software/Geant4/UCL HEP Cluster|UCL HEP Cluster]]:

* The [[/DAWN|<code>DAWN</code>]] postscript renderer to support the DAWN visualisation driver.
* The [[/HepRApp|<code>HepRApp</code>]] Browser for use with the [http://www.slac.stanford.edu/~perl/heprep/ HepRep] visualisation driver.
* The [[/Java Analysis Studio|<code>Java Analysis Studio</code>]] (<code>JAS3</code>), along with the [[/Java Analysis Studio#WIRED4|<code>WIRED4 JAS Plug-IN</code>]] for use with the [http://www.slac.stanford.edu/~perl/heprep/ HepRep] visualisation driver.
* The [[/gMocren|<code>gMocren</code>]] volume visualiser for <code>Geant4</code> medical simulations.

== Geant4 Installation ==

; Website : http://geant4.web.cern.ch/geant4/
; Latest version : 10.0.2 (13 June 2014)
; Source tarball : <code>src/geant4/geant4.10.00.p02.tar.gz</code>

All the required software has now been installed, and <code>GEANT4</code> itself can finally be installed.

Notes:
* There are a number of ways to configure the software before building. Using the <code>ccmake</code> command, each configuration option can be set interactively. Alternatively, the cmake command below configures with the recommended options.
* The makefile doesn't support <code>make install prefix</code>, and so <code>DESTDIR</code> must be used instead, and the files moved after installation.

Installation commands:

<pre>
cmake \
-DCMAKE_INSTALL_PREFIX="/unix/pbt/software/dev/geant4.10.02" \
-DCMAKE_INSTALL_CONFIG_NAME="Release" \
-DGEANT4_BUILD_MULTITHREADED=ON \
-DGEANT4_INSTALL_DATA=ON \
-DGEANT4_BUILD_EXAMPLES=OFF \
-DGEANT4_BUILD_TESTS=OFF \
-DGEANT4_ENABLE_TESTING=OFF \
-DGEANT4_BUILD_STORE_TRAJECTORY=ON \
-DGEANT4_BUILD_VERBOSE_CODE=ON \
-DGEANT4_USE_G3TOG4=ON \
-DGEANT4_USE_GDML=ON \
-DGEANT4_USE_INVENTOR=ON \
-DGEANT4_USE_NETWORKDAWN=ON \
-DGEANT4_USE_NETWORKVRML=ON \
-DGEANT4_USE_OPENGL_X11=ON \
-DGEANT4_USE_QT=ON \
-DGEANT4_USE_RAYTRACER_X11=ON \
-DGEANT4_USE_SYSTEM_CLHEP=ON \
-DGEANT4_USE_SYSTEM_EXPAT=ON \
-DGEANT4_USE_SYSTEM_ZLIB=ON \
-DGEANT4_USE_USOLIDS=OFF \
-DGEANT4_USE_WT=OFF \
-DGEANT4_USE_XM=ON \
-DINVENTOR_INCLUDE_DIR=/unix/pbt/software/dev/Coin-3.1.3/include/ \
-DINVENTOR_LIBRARY=/unix/pbt/software/dev/Coin-3.1.3/lib/libCoin.so \
-DINVENTOR_SOXT_INCLUDE_DIR=/unix/pbt/software/dev/SoXt-1.3.0/include/ \
-DINVENTOR_SOXT_LIBRARY=/unix/pbt/software/dev/SoXt-1.3.0/lib/libSoXt.so \
-DMOTIF_INCLUDE_DIR=/usr/include \
-DMOTIF_LIBRARIES=/usr/lib64/libXm.so \
-DQT_QMAKE_EXECUTABLE=/unix/pbt/software/dev/qt-5.5.1/bin/qmake \
-DBUILD_SHARED_LIBS=ON \
-DBUILD_STATIC_LIBS=OFF \
-DCMAKE_COLOR_MAKEFILE=ON \
-DCMAKE_USE_RELATIVE_PATHS=OFF \
-DCMAKE_VERBOSE_MAKEFILE=OFF \
../../src/geant4.10.02

make
make install

</pre>

== Testing ==

=== Software package tests ===

=== GEANT4 built-in tests ===

The <code>GEANT4</code> software includes some system tests, which can be included in the installation command via the options <code>-DGEANT4_BUILD_TESTS=ON -DGEANT4_ENABLE_TESTING=ON</code>.
However, these tests are only used for testing of the system, and are not included in the distributed source tarballs, nor supported for use by end-users.
Therefore, these cannot easily be used for validation of the production system installation.

=== GEANT4 examples ===

One test of the <code>GEANT4</code> software after installation is to make sure that all examples can be run and produce the expected results.

Notes:
* The examples can be built at installation time using the command <code>-DGEANT4_BUILD_EXAMPLES=ON</code>, but this throws up a number of problems because not all installation requirements are met. It is easier to build and run the examples after the installation is complete.
* Environment variable <code>G4SHARE</code> is defined in the environment scripts <code>pbt.bashrc</code> and <code>pbt-dev.bashrc</code>, along with the variable <code>G4VERSION</code>. For the current installation, the location stored in this variable is <code>/unix/pbt/software/dev/share/Geant4-10.0.2</code>

The following errors and warnings were seen while configuring examples:
* Cannot find <code>AIDA</code> package
* Cannot find <code>HBOOK</code> package
* Cannot find <code>HepMC</code> package
* Cannot find <code>Pythia6</code> package
* Cannot find <code>GCCXML</code> These packages are optional, but some of the examples are designed to demonstrate the connection with these packages. Note that some filetypes, such as <code>AIDA</code> and <code>HBOOK</code>, do in fact have viewers installed in the PBT environments, but these are not available to the <code>GEANT4</code> system. This what the errors are reporting.

==== Basic examples ====

===== B1 =====

<pre>
cp -r ${G4SHARE}/examples/basic/B1 . mkdir build cd build cmake ../B1 make ./exampleB1 exampleB1.in | tee exampleB1.new.out grep -B0 -A3 "End of Global Run" exampleB1.out > exampleB1.old.results grep -B0 -A3 "End of Global Run" exampleB1.new.out > exampleB1.new.results diff exampleB1.old.results exampleB1.new.results
</pre>

There seem to be significant differences in the simulation results compared to the included <code>exampleB1.out</code> file.
The reason for these differences is unclear.

Software/Geant4/Installation

2016-06-05T21:03:09Z

LukasKikuchi: /* Geant4 Installation */

== Installation Of Geant4 And Supporting Packages ==

The [http://geant4.web.cern.ch/geant4/UserDocumentation/UsersGuides/InstallationGuide/html/index.html CERN Geant4 Installation Guide] provides extensive instructions on installing Geant4.
This provides an overview of the installation procedure, as well as a list of prerequisites and additional software that need to be installed alongside Geant4.

In addition, information is given on the installation procedure for this additional software and the location the software is installed on the [[Software/Geant4/UCL HEP Cluster|UCL HEP Linux Cluster]].

The <code>environment</code> described here is the combination of files, folders, settings and user interface that allow users to make use of <code>Geant4</code> and related software packages for particle beam therapy simulations.

Accessing the environment requires the following:
* Access to the filesystem and required folders.
* Terminal access to run simulations.
* A visualisation engine such as OpenGL on X (''optional'').
* Setting environment variables to point to installed software and scripts.

The order of installation is important, as some packages depend on having the other packages first.
In some cases, installations will be successful if carried out in the wrong order, but some features will be disabled that should be enabled.
The order of packages described below is the order in which these packages were installed into the PBT environment.

== Required Software ==

The list of required software is split into 2 categories:

* [[#Prerequisites|Prerequisites]] are those components that are required in order for some part of <code>Geant4</code> or the resulting simulation visualisations to function correctly;
* [[#Add Ons|Add Ons]] are optional pieces of software — normally visualisation software — that are installed on the [[Software/Geant4/UCL HEP Cluster|UCL HEP Linux Cluster]].

See the individually linked pages for information on building each of the components that do not ship by default.

=== Prerequisites ===

The [http://geant4.web.cern.ch/geant4/UserDocumentation/UsersGuides/InstallationGuide/html/index.html CERN Geant4 Installation Guide] provides extensive information on
[http://geant4.web.cern.ch/geant4/UserDocumentation/UsersGuides/InstallationGuide/html/ch01s02.html software that must be installed to compile Geant4 itself] and software required in order to
[http://geant4.web.cern.ch/geant4/UserDocumentation/UsersGuides/InstallationGuide/html/ch01s03.html compile optional components of Geant4].

These are:

* A C++11 compatible compiler: on Linux, this is [https://gcc.gnu.org <code>GCC</code>: the GNU Compiler Collection] which is installed by default.
* [[/CMake|<code>CMake</code>]] required for building the various <code>Geant4</code> simulations through <code>cmake</code> files.
* The [[/CLHEP|<code>CLHEP</code> Class Library]] that provides a range of foundation and utility classes needed for <code>Geant4</code> simulations.

* [https://www.opengl.org <code>OpenGL</code> headers and libraries] to provide support for <code>OpenGL</code> graphics (graphics card specific; installed by default on most Operating Systems).
* [https://en.wikipedia.org/wiki/X_Window_System <code>X11</code>] headers and libraries to provide support for the <code>X</code>-Window system (installed by default on <nowiki>*</nowiki>nix systems
* [[/Qt|<code>Qt4</code> or <code>Qt5</code> headers and libraries]] to provide support for the Qt user interface and visualisation.
* [[/Xerces-C|<code>Xerces-C++</code> headers and libraries]] compiled against the C++11 standard to provide support for GDML geometry descriptions.
* [http://www.opengroup.org/openmotif <code>Motif</code>] and X11 headers and libraries to provide support for the Motif user interface and visualisation (installed by default on Linux)
* [[/Coin3D|<code>Coin3D</code>]] for Open Inventor visualisation (<code>Coin3D</code> is a free implementation of Open Inventor). This requires the following libraries to be installed:
** The [[/Coin3D#simage|<code>simage</code>]] library with image format loaders and front-ends to common import libraries. <code>simage</code> is meant for use with applications which read image files as textures. '''<code>simage</code> must be installed before <code>Coin3D</code>'''.
** The [[/Coin3D#SoXt|<code>SoXt</code>]] open source InventorXt library, which is a GUI binding for using Open Inventor with Xt/Motif. <code>SoXt</code> must be installed after <code>Coin3D</code>.
** [[/Coin3D#SoQt|<code>SoQt</code>]] open source <code>Qt</code> GUI component toolkit library for <code>Coin3D</code>. <code>SoQt</code> must be installed after <code>Coin3D</code>.

=== Add Ons ===

The [http://geant4.web.cern.ch/geant4/UserDocumentation/UsersGuides/InstallationGuide/html/index.html CERN Geant4 Installation Guide] provides a range of
[http://geant4.web.cern.ch/geant4/UserDocumentation/UsersGuides/InstallationGuide/html/ch01s04.html software suggested for use with <code>Geant4</code>].
While none of these need to be installed for <code>Geant4</code> to compile and run, they are useful for visualising the resulting simulations.

The following subset is installed on the [[Software/Geant4/UCL HEP Cluster|UCL HEP Cluster]]:

* The [[/DAWN|<code>DAWN</code>]] postscript renderer to support the DAWN visualisation driver.
* The [[/HepRApp|<code>HepRApp</code>]] Browser for use with the [http://www.slac.stanford.edu/~perl/heprep/ HepRep] visualisation driver.
* The [[/Java Analysis Studio|<code>Java Analysis Studio</code>]] (<code>JAS3</code>), along with the [[/Java Analysis Studio#WIRED4|<code>WIRED4 JAS Plug-IN</code>]] for use with the [http://www.slac.stanford.edu/~perl/heprep/ HepRep] visualisation driver.
* The [[/gMocren|<code>gMocren</code>]] volume visualiser for <code>Geant4</code> medical simulations.

== Geant4 Installation ==

; Website : http://geant4.web.cern.ch/geant4/
; Latest version : 10.0.2 (13 June 2014)
; Source tarball : <code>src/geant4/geant4.10.00.p02.tar.gz</code>

All the required software has now been installed, and <code>GEANT4</code> itself can finally be installed.

Notes:
* There are a number of ways to configure the software before building. Using the <code>ccmake</code> command, each configuration option can be set interactively. Alternatively, the cmake command below configures with the recommended options.
* The makefile doesn't support <code>make install prefix</code>, and so <code>DESTDIR</code> must be used instead, and the files moved after installation.

Installation commands:

<pre>
cmake \
-DCMAKE_INSTALL_PREFIX="/unix/pbt/software/dev/geant4.10.02" \
-DCMAKE_INSTALL_CONFIG_NAME="Release" \
-DGEANT4_BUILD_MULTITHREADED=ON \
-DGEANT4_INSTALL_DATA=ON \
-DGEANT4_BUILD_EXAMPLES=OFF \
-DGEANT4_BUILD_TESTS=OFF \
-DGEANT4_ENABLE_TESTING=OFF \
-DGEANT4_BUILD_STORE_TRAJECTORY=ON \
-DGEANT4_BUILD_VERBOSE_CODE=ON \
-DGEANT4_USE_G3TOG4=ON \
-DGEANT4_USE_GDML=ON \
-DGEANT4_USE_INVENTOR=ON \
-DGEANT4_USE_NETWORKDAWN=ON \
-DGEANT4_USE_NETWORKVRML=ON \
-DGEANT4_USE_OPENGL_X11=ON \
-DGEANT4_USE_QT=ON \
-DGEANT4_USE_RAYTRACER_X11=ON \
-DGEANT4_USE_SYSTEM_CLHEP=ON \
-DGEANT4_USE_SYSTEM_EXPAT=ON \
-DGEANT4_USE_SYSTEM_ZLIB=OFF \
-DGEANT4_USE_USOLIDS=OFF \
-DGEANT4_USE_WT=OFF \
-DGEANT4_USE_XM=ON \
-DINVENTOR_INCLUDE_DIR=/unix/pbt/software/dev/Coin-3.1.3/include/ \
-DINVENTOR_LIBRARY=/unix/pbt/software/dev/Coin-3.1.3/lib/libCoin.so \
-DINVENTOR_SOXT_INCLUDE_DIR=/unix/pbt/software/dev/SoXt-1.3.0/include/ \
-DINVENTOR_SOXT_LIBRARY=/unix/pbt/software/dev/SoXt-1.3.0/lib/libSoXt.so \
-DQT_QMAKE_EXECUTABLE=/unix/pbt/software/dev/qt-5.5.1/bin/qmake \
-DBUILD_SHARED_LIBS=ON \
-DBUILD_STATIC_LIBS=OFF \
-DCMAKE_COLOR_MAKEFILE=ON \
-DCMAKE_USE_RELATIVE_PATHS=OFF \
-DCMAKE_VERBOSE_MAKEFILE=OFF \
../../src/geant4.10.02

make
make install

</pre>

== Testing ==

=== Software package tests ===

=== GEANT4 built-in tests ===

The <code>GEANT4</code> software includes some system tests, which can be included in the installation command via the options <code>-DGEANT4_BUILD_TESTS=ON -DGEANT4_ENABLE_TESTING=ON</code>.
However, these tests are only used for testing of the system, and are not included in the distributed source tarballs, nor supported for use by end-users.
Therefore, these cannot easily be used for validation of the production system installation.

=== GEANT4 examples ===

One test of the <code>GEANT4</code> software after installation is to make sure that all examples can be run and produce the expected results.

Notes:
* The examples can be built at installation time using the command <code>-DGEANT4_BUILD_EXAMPLES=ON</code>, but this throws up a number of problems because not all installation requirements are met. It is easier to build and run the examples after the installation is complete.
* Environment variable <code>G4SHARE</code> is defined in the environment scripts <code>pbt.bashrc</code> and <code>pbt-dev.bashrc</code>, along with the variable <code>G4VERSION</code>. For the current installation, the location stored in this variable is <code>/unix/pbt/software/dev/share/Geant4-10.0.2</code>

The following errors and warnings were seen while configuring examples:
* Cannot find <code>AIDA</code> package
* Cannot find <code>HBOOK</code> package
* Cannot find <code>HepMC</code> package
* Cannot find <code>Pythia6</code> package
* Cannot find <code>GCCXML</code> These packages are optional, but some of the examples are designed to demonstrate the connection with these packages. Note that some filetypes, such as <code>AIDA</code> and <code>HBOOK</code>, do in fact have viewers installed in the PBT environments, but these are not available to the <code>GEANT4</code> system. This what the errors are reporting.

==== Basic examples ====

===== B1 =====

<pre>
cp -r ${G4SHARE}/examples/basic/B1 . mkdir build cd build cmake ../B1 make ./exampleB1 exampleB1.in | tee exampleB1.new.out grep -B0 -A3 "End of Global Run" exampleB1.out > exampleB1.old.results grep -B0 -A3 "End of Global Run" exampleB1.new.out > exampleB1.new.results diff exampleB1.old.results exampleB1.new.results
</pre>

There seem to be significant differences in the simulation results compared to the included <code>exampleB1.out</code> file.
The reason for these differences is unclear.

Software/Geant4/Installation

2016-06-05T21:00:41Z

LukasKikuchi: /* Geant4 Installation */

== Installation Of Geant4 And Supporting Packages ==

The [http://geant4.web.cern.ch/geant4/UserDocumentation/UsersGuides/InstallationGuide/html/index.html CERN Geant4 Installation Guide] provides extensive instructions on installing Geant4.
This provides an overview of the installation procedure, as well as a list of prerequisites and additional software that need to be installed alongside Geant4.

In addition, information is given on the installation procedure for this additional software and the location the software is installed on the [[Software/Geant4/UCL HEP Cluster|UCL HEP Linux Cluster]].

The <code>environment</code> described here is the combination of files, folders, settings and user interface that allow users to make use of <code>Geant4</code> and related software packages for particle beam therapy simulations.

Accessing the environment requires the following:
* Access to the filesystem and required folders.
* Terminal access to run simulations.
* A visualisation engine such as OpenGL on X (''optional'').
* Setting environment variables to point to installed software and scripts.

The order of installation is important, as some packages depend on having the other packages first.
In some cases, installations will be successful if carried out in the wrong order, but some features will be disabled that should be enabled.
The order of packages described below is the order in which these packages were installed into the PBT environment.

== Required Software ==

The list of required software is split into 2 categories:

* [[#Prerequisites|Prerequisites]] are those components that are required in order for some part of <code>Geant4</code> or the resulting simulation visualisations to function correctly;
* [[#Add Ons|Add Ons]] are optional pieces of software — normally visualisation software — that are installed on the [[Software/Geant4/UCL HEP Cluster|UCL HEP Linux Cluster]].

See the individually linked pages for information on building each of the components that do not ship by default.

=== Prerequisites ===

The [http://geant4.web.cern.ch/geant4/UserDocumentation/UsersGuides/InstallationGuide/html/index.html CERN Geant4 Installation Guide] provides extensive information on
[http://geant4.web.cern.ch/geant4/UserDocumentation/UsersGuides/InstallationGuide/html/ch01s02.html software that must be installed to compile Geant4 itself] and software required in order to
[http://geant4.web.cern.ch/geant4/UserDocumentation/UsersGuides/InstallationGuide/html/ch01s03.html compile optional components of Geant4].

These are:

* A C++11 compatible compiler: on Linux, this is [https://gcc.gnu.org <code>GCC</code>: the GNU Compiler Collection] which is installed by default.
* [[/CMake|<code>CMake</code>]] required for building the various <code>Geant4</code> simulations through <code>cmake</code> files.
* The [[/CLHEP|<code>CLHEP</code> Class Library]] that provides a range of foundation and utility classes needed for <code>Geant4</code> simulations.

* [https://www.opengl.org <code>OpenGL</code> headers and libraries] to provide support for <code>OpenGL</code> graphics (graphics card specific; installed by default on most Operating Systems).
* [https://en.wikipedia.org/wiki/X_Window_System <code>X11</code>] headers and libraries to provide support for the <code>X</code>-Window system (installed by default on <nowiki>*</nowiki>nix systems
* [[/Qt|<code>Qt4</code> or <code>Qt5</code> headers and libraries]] to provide support for the Qt user interface and visualisation.
* [[/Xerces-C|<code>Xerces-C++</code> headers and libraries]] compiled against the C++11 standard to provide support for GDML geometry descriptions.
* [http://www.opengroup.org/openmotif <code>Motif</code>] and X11 headers and libraries to provide support for the Motif user interface and visualisation (installed by default on Linux)
* [[/Coin3D|<code>Coin3D</code>]] for Open Inventor visualisation (<code>Coin3D</code> is a free implementation of Open Inventor). This requires the following libraries to be installed:
** The [[/Coin3D#simage|<code>simage</code>]] library with image format loaders and front-ends to common import libraries. <code>simage</code> is meant for use with applications which read image files as textures. '''<code>simage</code> must be installed before <code>Coin3D</code>'''.
** The [[/Coin3D#SoXt|<code>SoXt</code>]] open source InventorXt library, which is a GUI binding for using Open Inventor with Xt/Motif. <code>SoXt</code> must be installed after <code>Coin3D</code>.
** [[/Coin3D#SoQt|<code>SoQt</code>]] open source <code>Qt</code> GUI component toolkit library for <code>Coin3D</code>. <code>SoQt</code> must be installed after <code>Coin3D</code>.

=== Add Ons ===

The [http://geant4.web.cern.ch/geant4/UserDocumentation/UsersGuides/InstallationGuide/html/index.html CERN Geant4 Installation Guide] provides a range of
[http://geant4.web.cern.ch/geant4/UserDocumentation/UsersGuides/InstallationGuide/html/ch01s04.html software suggested for use with <code>Geant4</code>].
While none of these need to be installed for <code>Geant4</code> to compile and run, they are useful for visualising the resulting simulations.

The following subset is installed on the [[Software/Geant4/UCL HEP Cluster|UCL HEP Cluster]]:

* The [[/DAWN|<code>DAWN</code>]] postscript renderer to support the DAWN visualisation driver.
* The [[/HepRApp|<code>HepRApp</code>]] Browser for use with the [http://www.slac.stanford.edu/~perl/heprep/ HepRep] visualisation driver.
* The [[/Java Analysis Studio|<code>Java Analysis Studio</code>]] (<code>JAS3</code>), along with the [[/Java Analysis Studio#WIRED4|<code>WIRED4 JAS Plug-IN</code>]] for use with the [http://www.slac.stanford.edu/~perl/heprep/ HepRep] visualisation driver.
* The [[/gMocren|<code>gMocren</code>]] volume visualiser for <code>Geant4</code> medical simulations.

== Geant4 Installation ==

; Website : http://geant4.web.cern.ch/geant4/
; Latest version : 10.0.2 (13 June 2014)
; Source tarball : <code>src/geant4/geant4.10.00.p02.tar.gz</code>

All the required software has now been installed, and <code>GEANT4</code> itself can finally be installed.

Notes:
* There are a number of ways to configure the software before building. Using the <code>ccmake</code> command, each configuration option can be set interactively. Alternatively, the cmake command below configures with the recommended options.
* The makefile doesn't support <code>make install prefix</code>, and so <code>DESTDIR</code> must be used instead, and the files moved after installation.

Installation commands:

<pre>
cmake \
-DCMAKE_INSTALL_PREFIX="/unix/pbt/software/dev/geant4.10.02" \
-DCMAKE_INSTALL_CONFIG_NAME="Release" \
-DGEANT4_BUILD_MULTITHREADED=ON \
-DGEANT4_INSTALL_DATA=ON \
-DGEANT4_BUILD_EXAMPLES=OFF \
-DGEANT4_BUILD_TESTS=OFF \
-DGEANT4_ENABLE_TESTING=OFF \
-DGEANT4_BUILD_STORE_TRAJECTORY=ON \
-DGEANT4_BUILD_VERBOSE_CODE=ON \
-DGEANT4_USE_G3TOG4=ON \
-DGEANT4_USE_GDML=ON \
-DGEANT4_USE_INVENTOR=ON \
-DGEANT4_USE_NETWORKDAWN=ON \
-DGEANT4_USE_NETWORKVRML=ON \
-DGEANT4_USE_OPENGL_X11=ON \
-DGEANT4_USE_QT=ON \
-DGEANT4_USE_RAYTRACER_X11=ON \
-DGEANT4_USE_SYSTEM_CLHEP=OFF \
-DGEANT4_USE_SYSTEM_EXPAT=ON \
-DGEANT4_USE_SYSTEM_ZLIB=OFF \
-DGEANT4_USE_USOLIDS=OFF \
-DGEANT4_USE_WT=OFF \
-DGEANT4_USE_XM=ON \
-DINVENTOR_INCLUDE_DIR=/unix/pbt/software/dev/Coin-3.1.3/include/ \
-DINVENTOR_LIBRARY=/unix/pbt/software/dev/Coin-3.1.3/lib/libCoin.so \
-DINVENTOR_SOXT_INCLUDE_DIR=/unix/pbt/software/dev/SoXt-1.3.0/include/ \
-DINVENTOR_SOXT_LIBRARY=/unix/pbt/software/dev/SoXt-1.3.0/lib/libSoXt.so \
-DQT_QMAKE_EXECUTABLE=/unix/pbt/software/dev/qt-5.5.1/bin/qmake \
-DBUILD_SHARED_LIBS=ON \
-DBUILD_STATIC_LIBS=OFF \
-DCMAKE_COLOR_MAKEFILE=ON \
-DCMAKE_USE_RELATIVE_PATHS=OFF \
-DCMAKE_VERBOSE_MAKEFILE=OFF \
../../src/geant4.10.02

make
make install

</pre>

== Testing ==

=== Software package tests ===

=== GEANT4 built-in tests ===

The <code>GEANT4</code> software includes some system tests, which can be included in the installation command via the options <code>-DGEANT4_BUILD_TESTS=ON -DGEANT4_ENABLE_TESTING=ON</code>.
However, these tests are only used for testing of the system, and are not included in the distributed source tarballs, nor supported for use by end-users.
Therefore, these cannot easily be used for validation of the production system installation.

=== GEANT4 examples ===

One test of the <code>GEANT4</code> software after installation is to make sure that all examples can be run and produce the expected results.

Notes:
* The examples can be built at installation time using the command <code>-DGEANT4_BUILD_EXAMPLES=ON</code>, but this throws up a number of problems because not all installation requirements are met. It is easier to build and run the examples after the installation is complete.
* Environment variable <code>G4SHARE</code> is defined in the environment scripts <code>pbt.bashrc</code> and <code>pbt-dev.bashrc</code>, along with the variable <code>G4VERSION</code>. For the current installation, the location stored in this variable is <code>/unix/pbt/software/dev/share/Geant4-10.0.2</code>

The following errors and warnings were seen while configuring examples:
* Cannot find <code>AIDA</code> package
* Cannot find <code>HBOOK</code> package
* Cannot find <code>HepMC</code> package
* Cannot find <code>Pythia6</code> package
* Cannot find <code>GCCXML</code> These packages are optional, but some of the examples are designed to demonstrate the connection with these packages. Note that some filetypes, such as <code>AIDA</code> and <code>HBOOK</code>, do in fact have viewers installed in the PBT environments, but these are not available to the <code>GEANT4</code> system. This what the errors are reporting.

==== Basic examples ====

===== B1 =====

<pre>
cp -r ${G4SHARE}/examples/basic/B1 . mkdir build cd build cmake ../B1 make ./exampleB1 exampleB1.in | tee exampleB1.new.out grep -B0 -A3 "End of Global Run" exampleB1.out > exampleB1.old.results grep -B0 -A3 "End of Global Run" exampleB1.new.out > exampleB1.new.results diff exampleB1.old.results exampleB1.new.results
</pre>

There seem to be significant differences in the simulation results compared to the included <code>exampleB1.out</code> file.
The reason for these differences is unclear.

Software/Geant4/Installation/Coin3D

2016-06-05T20:56:11Z

LukasKikuchi: /* Fix Errors In Coin3D Code */

== Introduction ==

<code>Coin3D</code> is a high-level, retained-mode toolkit for effective 3D graphics development.
It is API compatible with Open Inventor 2.1.

<code>Geant4</code> requires the <code>Coin3D</code> headers and libraries in order to provide support for [https://en.wikipedia.org/wiki/Open_Inventor Open Inventor] visualisations.

In order to function correctly, <code>Coin3D</code> requires the following additional components to be installed:

* The [[#simage|<code>simage</code>]] library with image format loaders and front-ends to common import libraries. <code>simage</code> is meant for use with applications which read image files as textures. '''<code>simage</code> must be installed before <code>Coin3D</code>'''.
* The [[#SoXt|<code>SoXt</code>]] open source InventorXt library, which is a GUI binding for using Open Inventor with Xt/Motif. <code>SoXt</code> has been developed for use with <code>Coin3D</code>. <code>SoXt</code> needs to be installed after <code>Coin3D</code>'''.
* [[#SoQt|<code>SoXt</code>]] open source <code>Qt</code> GUI component toolkit library for <code>Coin3D</code>. <code>SoQt</code> needs to be installed after <code>Coin3D</code>'''.

== Details ==

=== <code>Coin3D</code> ===

; Website : https://bitbucket.org/Coin3D/coin/
; Source URL : https://bitbucket.org/Coin3D/coin/downloads
; Installed version : 3.1.3 (13 February 2012)
; Source tarball : <code>src/geant4-prerequisites/coin3d/Coin3d-3.1.3.tar.gz</code>

=== <code>simage</code> ===

; Website : https://bitbucket.org/Coin3D/simage
; Source URL : https://bitbucket.org/Coin3D/coin/downloads/simage-1.7.0.tar.gz
; Installed version : 1.7.0 (13 February 2012)
; Source tarball : <code>src/geant4-prerequisites/coin3d/simage-1.7.0.tar.gz</code>

=== <code>SoXt</code> ===

; Website : https://bitbucket.org/Coin3D/soxt
; Source URL : https://bitbucket.org/Coin3D/coin/downloads/SoXt-1.3.0.tar.gz
; Installed version : 1.3.0 (13 February 2012)
; Source tarball : <code>src/geant4-prerequisites/coin3d/SoXt-1.3.0.tar.gz</code>

=== <code>SoQt</code> ===

; Website : https://bitbucket.org/Coin3D/soqt
; Source URL : https://bitbucket.org/Coin3D/coin/downloads/SoQt-1.5.0.tar.gz
; Installed version : 1.5.0 (13 February 2012)
; Source tarball : <code>src/geant4-prerequisites/coin3d/SoXt-1.5.0.tar.gz</code>

== Installation Notes ==

The [https://bitbucket.org/Coin3D/coin/wiki/How%20to%20build%20Coin3D%20and%20SIM%20Voleon <code>Coin3D</code> documentation] provides some useful instructions on building and installing <code>Coin3D</code>.

For installation, <code>Coin3D</code> and the required libraries do not support installation into a sandbox directory (i.e. there are no options <code>prefix</code> or <code>DESTDIR</code> defined for command <code>make install</code>) and must be given the installation directory with the <code>--prefix</code> option.
As such, to recompile <code>Coin3D</code> for different target directories, the <code>configure</code> script must be rerun with a modified <code>--prefix /path/to/dest</code> option.
This has to be managed manually as can be seen in the installation commands below.

<code>Coin3D</code> and each of the components contain a number of programming errors.
Most can be ignored and skipped over by adding the compiler flag <code>-fpermissive</code> at the configuration step.

However, there is an error in the <code>Coin3D</code> source code that needs to be fixed before the code will compile: details on how to do so are given below.

<code>SoXt</code> may require the following modifications to install correctly:

* The configuration tool cannot find the libraries it needs unless the environment variable LD_RUN_PATH is manually set to include <code>/unix/pbt/software/prod-sl6/lib</code> (set automatically by the environment scripts on the [[/Software/Geant4/UCL HEP Cluster|UCL HEP Cluster]]).
* For older versions of SoXt and SoQt, part of the code required for compilation was removed to a separate project called <code>SoGUI</code>. This GUI code needed to be incorporated into the library code before compilation. The <code>SoGUI</code> source code is available in a separate tarball, <code>src/geant4- prerequisites/coin3d/sogui-2011-12-03.tar.gz</code>. The more recent versions of the <code>Coin3D</code> components now incorporate this code by default.

== Installation ==

When downloading software, the downloaded tarball (or other <code>Zip</code> archive) should be placed in an appropriately named directory in <code>/unix/pbt/software/src</code>: the instructions below assume that the directory is <code>/unix/pbt/software/src/geant4-prerequisites/coin3d</code>.

The source code should then be extracted into a suitable subdirectory in <code>/unix/pbt/software/build</code>.
The extracted source code directory can only be deleted once the software has been built and installed.

Instructions are given for compiling each component of <code>Coin3D</code>: '''these must be followed in order'''.

=== Source Code Extraction ===

<pre>
cd /unix/pbt/software/src/geant4-prerequisites/coin3d
tar -xvz -f simage-1.7.0.tar.gz
tar -xvz -f Coin-3.1.3.tar.gz
tar -xvz -f SoXt-1.3.0.tar.gz
tar -xvz -f SoQt-1.5.0.tar.gz
</pre>

=== Fix Errors In <code>Coin3D</code> Code ===

<code>Coin3D</code> and each of the components contain a number of programming errors.
Most can be ignored and skipped over by adding the compiler flag <code>-fpermissive</code> at the configuration step.

However, there is an error in the <code>Coin3D</code> source code that needs to be fixed before the code will compile:

* In the <code>Coin3D</code> source directory, find the directory <code>src/fonts/</code> and open the file <code>src/fonts/freetype.cpp</code>.
* Insert the following two lines in <code>src/fonts/freetype.cpp</code> before the line <code>#include fonts/freetype.h</code>:
** <code><nowiki>#include <cstdlib></nowiki></code>
** <code><nowiki>#include <cmath></nowiki></code>

The code should now compile successfully.

=== Further modifications to enable compiling Geant4 with OpenInventor ===

Geant4 compilation with OpenInventor enabled will fail unless an additional modification is made to the Coin3D source code.

Open the file <code>/include/Inventor/SbBasic.h</code> inside the Coin3D source, and add the following line below <code>#include <Inventor/C/basic.h></code>:

<pre>
#include <Inventor/C/errors/debugerror.h>
</pre>

=== Build And Install ===

It is possible to build for the '''Production''' environment without deleting the <code>Coin3D build</code> directory created for the '''Development''' installation, meaning that significant time is saved when running <code>make</code>.
However, it isn't recommended to do so as the '''Production''' installation ends up referencing components within <code>/unix/pbt/software/dev</code> which is not desirable as the two environments are no longer independent.
As such, these instructions assume one is building from scratch for each environment: to do so, make sure that the <code>build/coin3d</code> directory is deleted before recreating it for the subsequent build and install.

Also, although it is possible to install straight to the '''Production''' environment, it is highly discouraged to do so without first compiling a '''Development''' version.

==== Development Environment: <code>simage</code> ====

<pre>
cd /unix/pbt/software/build
mkdir -pv coin3d/simage-1.7.0
cd coin3d/simage-1.7.0
../../../src/geant4-prerequisites/coin3d/simage-1.7.0/configure --prefix /unix/pbt/software/dev/simage-1.7.0 CXXFLAGS=-fpermissive
make
make install
</pre>

==== Development Environment: <code>Coin3D</code> ====

<pre>
cd /unix/pbt/software/build
mkdir -pv coin3d/Coin-3.1.3
cd coin3d/Coin-3.1.3
../../../src/geant4-prerequisites/coin3d/Coin-3.1.3/configure --prefix /unix/pbt/software/dev/Coin-3.1.3 CXXFLAGS=-fpermissive
make
make install
</pre>

==== Development Environment: <code>SoXt</code> ====

<pre>
cd /unix/pbt/software/build
mkdir -pv coin3d/SoXt-1.3.0
cd coin3d/SoXt-1.3.0
../../../src/geant4-prerequisites/coin3d/SoXt-1.3.0/configure --prefix /unix/pbt/software/dev/SoXt-1.3.0 CXXFLAGS=-fpermissive
make
make install
</pre>

==== Development Environment: <code>SoXt</code> ====

<pre>
cd /unix/pbt/software/build
mkdir -pv coin3d/SoQt-1.5.0
cd coin3d/SoQt-1.5.0
../../../src/geant4-prerequisites/coin3d/SoQt-1.5.0/configure --prefix /unix/pbt/software/dev/SoQt-1.5.0 CXXFLAGS=-fpermissive
make
make install
</pre>

==== Production Environment: <code>simage</code> ====

<pre>
cd /unix/pbt/software/build
mkdir -pv coin3d/simage-1.7.0
cd coin3d/simage-1.7.0
../../../src/geant4-prerequisites/coin3d/simage-1.7.0/configure --prefix /unix/pbt/software/prod-sl6 CXXFLAGS=-fpermissive
make
make install
</pre>

==== Production Environment: <code>Coin3D</code> ====

<pre>
cd /unix/pbt/software/build
mkdir -pv coin3d/Coin-3.1.3
cd coin3d/Coin-3.1.3
../../../src/geant4-prerequisites/coin3d/Coin-3.1.3/configure --prefix /unix/pbt/software/prod-sl6 CXXFLAGS=-fpermissive
make
make install
</pre>

==== Production Environment: <code>SoXt</code> ====

<pre>
cd /unix/pbt/software/build
mkdir -pv coin3d/SoXt-1.3.0
cd coin3d/SoXt-1.3.0
../../../src/geant4-prerequisites/coin3d/SoXt-1.3.0/configure --prefix /unix/pbt/software/prod-sl6 CXXFLAGS=-fpermissive
make
make install
</pre>

==== Production Environment: <code>SoQt</code> ====

<pre>
cd /unix/pbt/software/build
mkdir -pv coin3d/SoQt-1.5.0
cd coin3d/SoQt-1.5.0
../../../src/geant4-prerequisites/coin3d/SoQt-1.5.0/configure --prefix /unix/pbt/software/prod-sl6 CXXFLAGS=-fpermissive
make
make install
</pre>

Software/Geant4/Installation/Coin3D

2016-06-05T20:46:39Z

LukasKikuchi:

== Introduction ==

<code>Coin3D</code> is a high-level, retained-mode toolkit for effective 3D graphics development.
It is API compatible with Open Inventor 2.1.

<code>Geant4</code> requires the <code>Coin3D</code> headers and libraries in order to provide support for [https://en.wikipedia.org/wiki/Open_Inventor Open Inventor] visualisations.

In order to function correctly, <code>Coin3D</code> requires the following additional components to be installed:

* The [[#simage|<code>simage</code>]] library with image format loaders and front-ends to common import libraries. <code>simage</code> is meant for use with applications which read image files as textures. '''<code>simage</code> must be installed before <code>Coin3D</code>'''.
* The [[#SoXt|<code>SoXt</code>]] open source InventorXt library, which is a GUI binding for using Open Inventor with Xt/Motif. <code>SoXt</code> has been developed for use with <code>Coin3D</code>. <code>SoXt</code> needs to be installed after <code>Coin3D</code>'''.
* [[#SoQt|<code>SoXt</code>]] open source <code>Qt</code> GUI component toolkit library for <code>Coin3D</code>. <code>SoQt</code> needs to be installed after <code>Coin3D</code>'''.

== Details ==

=== <code>Coin3D</code> ===

; Website : https://bitbucket.org/Coin3D/coin/
; Source URL : https://bitbucket.org/Coin3D/coin/downloads
; Installed version : 3.1.3 (13 February 2012)
; Source tarball : <code>src/geant4-prerequisites/coin3d/Coin3d-3.1.3.tar.gz</code>

=== <code>simage</code> ===

; Website : https://bitbucket.org/Coin3D/simage
; Source URL : https://bitbucket.org/Coin3D/coin/downloads/simage-1.7.0.tar.gz
; Installed version : 1.7.0 (13 February 2012)
; Source tarball : <code>src/geant4-prerequisites/coin3d/simage-1.7.0.tar.gz</code>

=== <code>SoXt</code> ===

; Website : https://bitbucket.org/Coin3D/soxt
; Source URL : https://bitbucket.org/Coin3D/coin/downloads/SoXt-1.3.0.tar.gz
; Installed version : 1.3.0 (13 February 2012)
; Source tarball : <code>src/geant4-prerequisites/coin3d/SoXt-1.3.0.tar.gz</code>

=== <code>SoQt</code> ===

; Website : https://bitbucket.org/Coin3D/soqt
; Source URL : https://bitbucket.org/Coin3D/coin/downloads/SoQt-1.5.0.tar.gz
; Installed version : 1.5.0 (13 February 2012)
; Source tarball : <code>src/geant4-prerequisites/coin3d/SoXt-1.5.0.tar.gz</code>

== Installation Notes ==

The [https://bitbucket.org/Coin3D/coin/wiki/How%20to%20build%20Coin3D%20and%20SIM%20Voleon <code>Coin3D</code> documentation] provides some useful instructions on building and installing <code>Coin3D</code>.

For installation, <code>Coin3D</code> and the required libraries do not support installation into a sandbox directory (i.e. there are no options <code>prefix</code> or <code>DESTDIR</code> defined for command <code>make install</code>) and must be given the installation directory with the <code>--prefix</code> option.
As such, to recompile <code>Coin3D</code> for different target directories, the <code>configure</code> script must be rerun with a modified <code>--prefix /path/to/dest</code> option.
This has to be managed manually as can be seen in the installation commands below.

<code>Coin3D</code> and each of the components contain a number of programming errors.
Most can be ignored and skipped over by adding the compiler flag <code>-fpermissive</code> at the configuration step.

However, there is an error in the <code>Coin3D</code> source code that needs to be fixed before the code will compile: details on how to do so are given below.

<code>SoXt</code> may require the following modifications to install correctly:

* The configuration tool cannot find the libraries it needs unless the environment variable LD_RUN_PATH is manually set to include <code>/unix/pbt/software/prod-sl6/lib</code> (set automatically by the environment scripts on the [[/Software/Geant4/UCL HEP Cluster|UCL HEP Cluster]]).
* For older versions of SoXt and SoQt, part of the code required for compilation was removed to a separate project called <code>SoGUI</code>. This GUI code needed to be incorporated into the library code before compilation. The <code>SoGUI</code> source code is available in a separate tarball, <code>src/geant4- prerequisites/coin3d/sogui-2011-12-03.tar.gz</code>. The more recent versions of the <code>Coin3D</code> components now incorporate this code by default.

== Installation ==

When downloading software, the downloaded tarball (or other <code>Zip</code> archive) should be placed in an appropriately named directory in <code>/unix/pbt/software/src</code>: the instructions below assume that the directory is <code>/unix/pbt/software/src/geant4-prerequisites/coin3d</code>.

The source code should then be extracted into a suitable subdirectory in <code>/unix/pbt/software/build</code>.
The extracted source code directory can only be deleted once the software has been built and installed.

Instructions are given for compiling each component of <code>Coin3D</code>: '''these must be followed in order'''.

=== Source Code Extraction ===

<pre>
cd /unix/pbt/software/src/geant4-prerequisites/coin3d
tar -xvz -f simage-1.7.0.tar.gz
tar -xvz -f Coin-3.1.3.tar.gz
tar -xvz -f SoXt-1.3.0.tar.gz
tar -xvz -f SoQt-1.5.0.tar.gz
</pre>

=== Fix Errors In <code>Coin3D</code> Code ===

<code>Coin3D</code> and each of the components contain a number of programming errors.
Most can be ignored and skipped over by adding the compiler flag <code>-fpermissive</code> at the configuration step.

However, there is an error in the <code>Coin3D</code> source code that needs to be fixed before the code will compile:

* In the <code>Coin3D</code> source directory, find the directory <code>src/fonts/</code> and open the file <code>src/fonts/freetype.cpp</code>.
* Insert the following two lines in <code>src/fonts/freetype.cpp</code> before the line <code>#include fonts/freetype.h</code>:
** <code><nowiki>#include <cstdlib></nowiki></code>
** <code><nowiki>#include <cmath></nowiki></code>

The code should now compile successfully.

=== Build And Install ===

It is possible to build for the '''Production''' environment without deleting the <code>Coin3D build</code> directory created for the '''Development''' installation, meaning that significant time is saved when running <code>make</code>.
However, it isn't recommended to do so as the '''Production''' installation ends up referencing components within <code>/unix/pbt/software/dev</code> which is not desirable as the two environments are no longer independent.
As such, these instructions assume one is building from scratch for each environment: to do so, make sure that the <code>build/coin3d</code> directory is deleted before recreating it for the subsequent build and install.

Also, although it is possible to install straight to the '''Production''' environment, it is highly discouraged to do so without first compiling a '''Development''' version.

==== Development Environment: <code>simage</code> ====

<pre>
cd /unix/pbt/software/build
mkdir -pv coin3d/simage-1.7.0
cd coin3d/simage-1.7.0
../../../src/geant4-prerequisites/coin3d/simage-1.7.0/configure --prefix /unix/pbt/software/dev/simage-1.7.0 CXXFLAGS=-fpermissive
make
make install
</pre>

==== Development Environment: <code>Coin3D</code> ====

<pre>
cd /unix/pbt/software/build
mkdir -pv coin3d/Coin-3.1.3
cd coin3d/Coin-3.1.3
../../../src/geant4-prerequisites/coin3d/Coin-3.1.3/configure --prefix /unix/pbt/software/dev/Coin-3.1.3 CXXFLAGS=-fpermissive
make
make install
</pre>

==== Development Environment: <code>SoXt</code> ====

<pre>
cd /unix/pbt/software/build
mkdir -pv coin3d/SoXt-1.3.0
cd coin3d/SoXt-1.3.0
../../../src/geant4-prerequisites/coin3d/SoXt-1.3.0/configure --prefix /unix/pbt/software/dev/SoXt-1.3.0 CXXFLAGS=-fpermissive
make
make install
</pre>

==== Development Environment: <code>SoXt</code> ====

<pre>
cd /unix/pbt/software/build
mkdir -pv coin3d/SoQt-1.5.0
cd coin3d/SoQt-1.5.0
../../../src/geant4-prerequisites/coin3d/SoQt-1.5.0/configure --prefix /unix/pbt/software/dev/SoQt-1.5.0 CXXFLAGS=-fpermissive
make
make install
</pre>

==== Production Environment: <code>simage</code> ====

<pre>
cd /unix/pbt/software/build
mkdir -pv coin3d/simage-1.7.0
cd coin3d/simage-1.7.0
../../../src/geant4-prerequisites/coin3d/simage-1.7.0/configure --prefix /unix/pbt/software/prod-sl6 CXXFLAGS=-fpermissive
make
make install
</pre>

==== Production Environment: <code>Coin3D</code> ====

<pre>
cd /unix/pbt/software/build
mkdir -pv coin3d/Coin-3.1.3
cd coin3d/Coin-3.1.3
../../../src/geant4-prerequisites/coin3d/Coin-3.1.3/configure --prefix /unix/pbt/software/prod-sl6 CXXFLAGS=-fpermissive
make
make install
</pre>

==== Production Environment: <code>SoXt</code> ====

<pre>
cd /unix/pbt/software/build
mkdir -pv coin3d/SoXt-1.3.0
cd coin3d/SoXt-1.3.0
../../../src/geant4-prerequisites/coin3d/SoXt-1.3.0/configure --prefix /unix/pbt/software/prod-sl6 CXXFLAGS=-fpermissive
make
make install
</pre>

==== Production Environment: <code>SoQt</code> ====

<pre>
cd /unix/pbt/software/build
mkdir -pv coin3d/SoQt-1.5.0
cd coin3d/SoQt-1.5.0
../../../src/geant4-prerequisites/coin3d/SoQt-1.5.0/configure --prefix /unix/pbt/software/prod-sl6 CXXFLAGS=-fpermissive
make
make install
</pre>

Software/Geant4/Installation/Xerces-C

2016-06-05T20:43:49Z

LukasKikuchi: /* Production Environment */

== Introduction ==

<code>Xerces-C++</code> is a validating XML parser written in a portable subset of C++. Xerces-C++ makes it easy to give your application the ability to read and write XML data.

<code>Geant4</code> requires the <code>Xerces-C++</code> headers and libraries compiled against the C++11 standard in order to provide support for GDML geometry descriptions.

== Details ==

; Website : http://xerces.apache.org/xerces-c/
; Source URL : http://www.apache.org/dist/xerces/c/3/sources/
; Installed version : 3.1.3 (17 Feb 2016)
; Source code : <code>src/geant4-prerequisites/xerces-c/xerces-c-3.1.3.tar.gz</code>

== Installation Notes ==

The [http://xerces.apache.org/xerces-c/ Xerces-C++ website] provides some useful instructions on [http://xerces.apache.org/xerces-c/build-3.html Building and Installing Xerces-C++].

For installation, <code>Xerces-C++</code> does not support installation into a sandbox directory (i.e. there are no options <code>prefix</code> or <code>DESTDIR</code> defined for command <code>make install</code>) and must be given the installation directory with the <code>-prefix</code> option.
As such, to recompile <code>Xerces-C++</code> for different target directories, the <code>configure</code> script must be rerun with a modified <code>-prefix /path/to/dest</code> option.
This has to be managed manually as can be seen in the installation commands below.

== Installation ==

When downloading software, the downloaded tarball (or other <code>Zip</code> archive) should be placed in an appropriately named directory in <code>/unix/pbt/software/src</code>: the instructions below assume that the directory is <code>/unix/pbt/software/src/geant4-prerequisites/xerces-c</code>.

The source code should then be extracted into a suitable subdirectory in <code>/unix/pbt/software/build</code>.
The extracted source code directory can only be deleted once the software has been built and installed.

=== Source Code Extraction ===

<pre>
cd /unix/pbt/software/src/geant4-prerequisites/xerces-c
tar -xvz -f xerces-c-3.1.3.tar.gz
</pre>

=== Build And Install ===

It is possible to build for the '''Production''' environment without deleting the <code>Xerces-C build</code> directory created for the '''Development''' installation, meaning that significant time is saved when running <code>make</code>.
However, it isn't recommended to do so as the '''Production''' installation ends up referencing components within <code>/unix/pbt/software/dev</code> which is not desirable as the two environments are no longer independent.
As such, these instructions assume one is building from scratch for each environment: to do so, make sure that the <code>build/qt</code> directory is deleted before recreating it for the subsequent build and install.

Also, although it is possible to install straight to the '''Production''' environment, it is highly discouraged to do so without first compiling a '''Development''' version.

==== Development Environment ====

<pre>
cd /unix/pbt/software/build
mkdir -pv xerces-c/xerces-c-3.1.3
cd xerces-c/xerces-c-3.1.3
../../../src/geant4-prerequisites/xerces-c/xerces-c/configure --prefix /unix/pbt/software/dev/xerces-c-3.1.3
make
make install
</pre>

==== Production Environment ====

<pre>
cd /unix/pbt/software/build
mkdir -pv xerces-c/xerces-c-3.1.3
cd xerces-c/xerces-c-3.1.3
../../../src/geant4-prerequisites/xerces-c/xerces-c/configure --prefix /unix/pbt/software/prod-sl6
make
make install
</pre>

Software/Geant4/Installation/Xerces-C

2016-06-05T20:43:40Z

LukasKikuchi: /* Development Environment */

== Introduction ==

<code>Xerces-C++</code> is a validating XML parser written in a portable subset of C++. Xerces-C++ makes it easy to give your application the ability to read and write XML data.

<code>Geant4</code> requires the <code>Xerces-C++</code> headers and libraries compiled against the C++11 standard in order to provide support for GDML geometry descriptions.

== Details ==

; Website : http://xerces.apache.org/xerces-c/
; Source URL : http://www.apache.org/dist/xerces/c/3/sources/
; Installed version : 3.1.3 (17 Feb 2016)
; Source code : <code>src/geant4-prerequisites/xerces-c/xerces-c-3.1.3.tar.gz</code>

== Installation Notes ==

The [http://xerces.apache.org/xerces-c/ Xerces-C++ website] provides some useful instructions on [http://xerces.apache.org/xerces-c/build-3.html Building and Installing Xerces-C++].

For installation, <code>Xerces-C++</code> does not support installation into a sandbox directory (i.e. there are no options <code>prefix</code> or <code>DESTDIR</code> defined for command <code>make install</code>) and must be given the installation directory with the <code>-prefix</code> option.
As such, to recompile <code>Xerces-C++</code> for different target directories, the <code>configure</code> script must be rerun with a modified <code>-prefix /path/to/dest</code> option.
This has to be managed manually as can be seen in the installation commands below.

== Installation ==

When downloading software, the downloaded tarball (or other <code>Zip</code> archive) should be placed in an appropriately named directory in <code>/unix/pbt/software/src</code>: the instructions below assume that the directory is <code>/unix/pbt/software/src/geant4-prerequisites/xerces-c</code>.

The source code should then be extracted into a suitable subdirectory in <code>/unix/pbt/software/build</code>.
The extracted source code directory can only be deleted once the software has been built and installed.

=== Source Code Extraction ===

<pre>
cd /unix/pbt/software/src/geant4-prerequisites/xerces-c
tar -xvz -f xerces-c-3.1.3.tar.gz
</pre>

=== Build And Install ===

It is possible to build for the '''Production''' environment without deleting the <code>Xerces-C build</code> directory created for the '''Development''' installation, meaning that significant time is saved when running <code>make</code>.
However, it isn't recommended to do so as the '''Production''' installation ends up referencing components within <code>/unix/pbt/software/dev</code> which is not desirable as the two environments are no longer independent.
As such, these instructions assume one is building from scratch for each environment: to do so, make sure that the <code>build/qt</code> directory is deleted before recreating it for the subsequent build and install.

Also, although it is possible to install straight to the '''Production''' environment, it is highly discouraged to do so without first compiling a '''Development''' version.

==== Development Environment ====

<pre>
cd /unix/pbt/software/build
mkdir -pv xerces-c/xerces-c-3.1.3
cd xerces-c/xerces-c-3.1.3
../../../src/geant4-prerequisites/xerces-c/xerces-c/configure --prefix /unix/pbt/software/dev/xerces-c-3.1.3
make
make install
</pre>

==== Production Environment ====

<pre>
cd /unix/pbt/software/build
mkdir -pv xerces-c/xerces-c-3.1.3
cd xerces-c/xerces-c-3.1.3
../../../src/geant4-prerequisites/xerces-c/xerces-c/configure -prefix /unix/pbt/software/prod-sl6
make
make install
</pre>