Install the binary distribution xerces-c-3.1.1-{arch}-{os}-{compiler}.tar.gz
by extracting the files from the compressed archive. Here {arch}
denotes the CPU architecture, {os} denotes the operating system,
and {compiler} denotes the C++ compiler of your choice.
For example:
 |  |  |
 |
gzip -d xerces-c-3.1.1-x86-linux-gcc-3.4.tar.gz
tar -xf xerces-c-3.1.1-x86-linux-gcc-3.4.tar
|  |
 |  |  |
This will create an 'xerces-c-3.1.1-x86-linux-gcc-3.4'
sub-directory containing the Xerces-C++ binary distribution.
You will need to add the
xerces-c-3.1.1-{arch}-{os}-{compiler}/bin directory to your
PATH environment variable:
For Bourne Shell, K Shell or Bash, type:
 |  |  |
 |
export PATH="$PATH:<full-path-to-xerces-c-3.1.1-{arch}-{os}-{compiler}>/bin"
|  |
 |  |  |
For C Shell, type:
 |  |  |
 |
setenv PATH "$PATH:<full-path-to-xerces-c-3.1.1-{arch}-{os}-{compiler}>/bin"
|  |
 |  |  |
If you wish to make this setting permanent, you need to change
your profile by changing your setup files which can be either
.profile or .kshrc.
In addition, you will also need to set the library search path.
(LIBPATH on AIX, LD_LIBRARY_PATH on Solaris and Linux,
SHLIB_PATH on HP-UX, and DYLD_LIBRARY_PATH on Mac OS X).
In the following shell commands, the <xerces-path>
denotes the full path to the
xerces-c-3.1.1-{arch}-{os}-{compiler} directory. For
Bourne Shell, K Shell or Bash, type:
 |  |  |
 |
export LIBPATH=<xerces-path>/lib:$LIBPATH (AIX)
export LD_LIBRARY_PATH=<xerces-path>/lib:$LD_LIBRARY_PATH (Solaris, Linux)
export SHLIB_PATH=<xerces-path>/lib:$SHLIB_PATH (HP-UX)
export DYLD_LIBRARY_PATH=<xerces-path>/lib:$DYLD_LIBRARY_PATH (Mac OS X)
|  |
 |  |  |
For C Shell, type:
 |  |  |
 |
setenv LIBPATH "<xerces-path>/lib:$LIBPATH" (AIX)
setenv LD_LIBRARY_PATH "<xerces-path>/lib:$LD_LIBRARY_PATH" (Solaris, Linux)
setenv SHLIB_PATH "<xerces-path>/lib:$SHLIB_PATH" (HP-UX)
setenv DYLD_LIBRARY_PATH "<xerces-path>/lib:$DYLD_LIBRARY_PATH" (Mac OS X)
|  |
 |  |  |
The binary distribution contains the pre-built parser libraries
and sample executables. Please refer to the
Samples for how to run the
samples.