Software/Geant4/Installation/Xerces-C - Revision history

JamesChappell: /* Installation from Central Repository */

2017-10-20T10:49:26Z

Installation from Central Repository

← Older revision		Revision as of 10:49, 20 October 2017
Line 46:		Line 46:
	</pre>		</pre>

	The command ccmake . opens an interactive GUI that can be used to specify installation options. From within this you can define your installation directory and configure any other options as required. On the PBT cluster it is required that the software is installed to the development directory, and so the CMAKE_INSTALL_PREFIX is defined as follows:		The command <code>ccmake .</code> opens an interactive GUI that can be used to specify installation options. From within this you can define your installation directory and configure any other options as required. On the PBT cluster it is required that the software is installed to the development directory, and so the <code>CMAKE_INSTALL_PREFIX</code> is defined as follows:

	<pre>		<pre>

JamesChappell at 10:19, 20 October 2017

2017-10-20T10:19:45Z

← Older revision		Revision as of 10:19, 20 October 2017
Line 9:		Line 9:
	; Website : http://xerces.apache.org/xerces-c/		; Website : http://xerces.apache.org/xerces-c/
	; Source URL : http://www.apache.org/dist/xerces/c/3/sources/		; Source URL : http://www.apache.org/dist/xerces/c/3/sources/
	; Installed version : 3.1.3 (17 Feb 2016)		; Installed Production version : 3.1.3 (17 Feb 2016)
	; Source code : <code>src/geant4-prerequisites/xerces-c/xerces-c-3.1.3.tar.gz</code>		; Source code : <code>src/geant4-prerequisites/xerces-c/xerces-c-3.1.3.tar.gz</code>
			; Installed Development version : 3.2.0 (20 October 2017)
			; Central Repository : https://github.com/apache/xerces-c

	== Installation Notes ==		== Installation Notes ==
Line 27:		Line 29:
	The extracted source code directory can only be deleted once the software has been built and installed.		The extracted source code directory can only be deleted once the software has been built and installed.

	=== Source Code Extraction ===		=== Installation from Central Repository ===

			After the latest version has been pulled from its [https://github.com/apache/xerces-c central repository] and placed within /unix/pbt/software/src/xerces-c, create a build directory within the PBT software directory from which you can compile the code:

			<pre>
			cd /unix/pbt/software/build/
			mkdir xerces-c
			cd xerces-c
			</pre>

			<code>CMake</code> can then be used to configure and install <code>Xerces-C</code>.

			<pre>
			cmake ../../src/xerces-c
			ccmake .
			</pre>

			The command ccmake . opens an interactive GUI that can be used to specify installation options. From within this you can define your installation directory and configure any other options as required. On the PBT cluster it is required that the software is installed to the development directory, and so the CMAKE_INSTALL_PREFIX is defined as follows:

			<pre>
			CMAKE_INSTALL_PREFIX /unix/pbt/software/dev/xerces-c-3.2
			</pre>

			*''c'' to configure
			*''g'' to generate and exit

			The software can then be installed using the usual commands:

			<pre>
			make
			make install
			</pre>

			=== Installation from source code ===

			==== Source Code Extraction ====

	<pre>		<pre>
Line 34:		Line 71:
	</pre>		</pre>

	=== Build And Install ===		==== 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>.		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>.
Line 42:		Line 79:
	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.		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 ====		===== Development Environment =====

	<pre>		<pre>
Line 53:		Line 90:
	</pre>		</pre>

	==== Production Environment ====		===== Production Environment =====

	<pre>		<pre>

LukasKikuchi: /* Production Environment */

2016-06-05T20:43:49Z

Production Environment

← Older revision		Revision as of 20:43, 5 June 2016
Line 59:		Line 59:
	mkdir -pv xerces-c/xerces-c-3.1.3		mkdir -pv xerces-c/xerces-c-3.1.3
	cd 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		../../../src/geant4-prerequisites/xerces-c/xerces-c/configure --prefix /unix/pbt/software/prod-sl6
	make		make
	make install		make install
	</pre>		</pre>

LukasKikuchi: /* Development Environment */

2016-06-05T20:43:40Z

Development Environment

← Older revision		Revision as of 20:43, 5 June 2016
Line 48:		Line 48:
	mkdir -pv xerces-c/xerces-c-3.1.3		mkdir -pv xerces-c/xerces-c-3.1.3
	cd 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		../../../src/geant4-prerequisites/xerces-c/xerces-c/configure --prefix /unix/pbt/software/dev/xerces-c-3.1.3
	make		make
	make install		make install

SimonJolly at 15:54, 24 May 2016

2016-05-24T15:54:41Z

← Older revision		Revision as of 15:54, 24 May 2016
Line 36:		Line 36:
	=== Build And Install ===		=== Build And Install ===

	~~These instructions assume the code has already been built~~ for the '''~~Development~~''' environment ~~before building~~ for the '''~~Production~~''' ~~environment~~, so ~~some of the commands for~~ the '''Production''' ~~install~~ are ~~omitted~~.		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>.
	~~Although~~ it is ~~highly discouraged~~ to install straight to the '''Production''' environment without first compiling a '''Development''' version~~, it is possible to do so by adding in the directory creation commands at the start~~.		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 ====		==== Development Environment ====
Line 53:		Line 56:

	<pre>		<pre>
	cd /unix/pbt/software/build/xerces-c/xerces-c-3.1.3		cd /unix/pbt/software/build
	../../../src/geant4-prerequisites/xerces-c/xerces-c/configure -prefix /unix/pbt/software/~~dev/xerces-c~~-~~3.1.3~~		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
	make install		make install
	</pre>		</pre>

SimonJolly: Created page with "== Introduction == `Xerces-C++` 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 ..."

2016-05-24T15:36:37Z

Created page with "== 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 ..."

New page

== 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 ===

These instructions assume the code has already been built for the '''Development''' environment before building for the '''Production''' environment, so some of the commands for the '''Production''' install are omitted.
Although it is highly discouraged to install straight to the '''Production''' environment without first compiling a '''Development''' version, it is possible to do so by adding in the directory creation commands at the start.

==== 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/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>