Trademark Logo Xalan-C/C++ Version 1.11
Installing Xalan-C++
Apache Foundation Xalan Project Xerces Project Web Consortium Oasis Open

Installing Xalan-C++

(top)

Install Source Packages

We have no package managers for source packages. You just extract the contents of the distribution zip or tar file into a source directory of your choosing.

The supplemental package building scripts for Linux and UNIX look for the Xalan-C sources to be found in a directory named xalan-src . The Xerces-C sources are expected to be found in a directory named xerces-src .

The supplemental package building scripts for Windows look for the Xalan-C sources to be found in a directory named xalan-src-11 and the Xerces-C sources to be found in a directory named xerces-src-31 .

When building the Xalan-C library and sample programs, you also need the necessary C/C++ compiler tools installed. A working copy of the Xerces-C XML parser library must be available before you can build the Xalan-C library. You may build the Xerces-C XML parser library from a source distribution or use a compatible Xerces-C binary distribution.

Building the User Guide web pages from sources requires a working Xalan command line program. The Xalan command-line program must support top-level parameters as strings.

Building the interactive API Reference pages requires a UNIX or Linux system with a current copy of Doxygen and GraphViz software installed.

(top)

Install Binary Packages

The binary packages distributed by zip and tar files are usually extracted to an install directory of your choosing. After extracting the contents, and possibly relocating some items, you may then need to manually perform some minor system configuration.

(top)

Install UNIX Binary Packages

Binary packages for Linux and UNIX systems only distribute a release build of binaries. A debug build of binaries requires you to compile from the sources. Binary packages for Linux and UNIX systems have the following directory structure.

./bin/ Contains the Xalan.exe command line and DLLs
./lib/ Contains the linker libraries
./include/xalanc/ Contains the Xalan-C header files
./doc/xalanc-1.11/ Contains license and other information

Supplemental scripts for Linux and UNIX builds are available in the source distribution by which binary packages can be made. The release builds are targeted to ${prefix} = /opt/apache/. The debug buids are targeted to ${prefix} = /opt/apache/debug/.

Packages that are released by a UNIX or Linux package manager are usually installed and configured by the package manager.

Configure UNIX and Linux Systems

The Xalan command line executable should be in a directory accessible by the PATH environment.

The lib directories containing the libxalan-c.so and libxerces-c.so objects must be known to the shared object loader. The system loader environment variable usually takes precedence over the shared object cache. I use the shared object cache for installed applications and reserve the overriding environment for prototype builds and debugging purposes.

Operating System Library Path Environment
Solaris and Linux LD_LIBRARY_PATH
BSD/GNU LD_LIBRARY_PATH
HP-UX SHLIB_PATH
AIX and BSD LIBPATH
MacOSX DYLD_LIBRARY_PATH
Cygwin and MinGW PATH

The library search path order is significant. In many cases, the /usr/lib , /lib , and /usr/local/lib paths are already cached in /etc/ld.so.cache or included by /etc/ld.so.conf .

(top)

Install Windows Binary Packages

Binary packages for Windows systems include a directory name related to the Windows Studio platform used to build the product. The {bin, lib, include, doc} directories are subdirectories of the platform directory. Libraries for several Visual Studio development systems can be installed on the same Windows computer.

XALANCPKG-11-31-VC71 for Visual Studio 2003 (Win32)
XALANCPKG-11-31-VC80 for Visual Studio 2005 (Win32)
XALANCPKG-11-31-VC90 for Visual Studio 2008 (Win32)
XALANCPKG-11-31-VC100 for Visual Studio 2010 (Win32)
XALANCPKG-11-31-X64-VC80 for Visual Studio 2005 (amd64)
XALANCPKG-11-31-X64-VC90 for Visual Studio 2008 (amd64)
XALANCPKG-11-31-X64-VC100 for Visual Studio 2010 (amd64)

Supplemental scripts for Windows builds are available in the source distribution by which these above binary packages can be made. Also included are scripts for building the Xerces-C sources to the following binary package directories. These directories are mostly compatible with the required XALANCROOT and XERCESCROOT environment variables when building your own applications.

XERCESCPKG-31-VC71 for Visual Studio 2003 (Win32)
XERCESCPKG-31-VC80 for Visual Studio 2005 (Win32)
XERCESCPKG-31-VC90 for Visual Studio 2008 (Win32)
XERCESCPKG-31-VC100 for Visual Studio 2010 (Win32)
XERCESCPKG-31-X64-VC80 for Visual Studio 2005 (amd64)
XERCESCPKG-31-X64-VC90 for Visual Studio 2008 (amd64)
XERCESCPKG-31-X64-VC100 for Visual Studio 2010 (amd64)

Supplemental scripts for Windows builds will also handle the packaging of older Xalan-C and Xerces-C releases. A similar naming of package directories and source directories is supported for these older releases.

note You MUST NOT merge the bin and lib directories from packages compiled with different compilers or different target (Win32 or amd64) platforms.

It is safe to merge the bin directories of compatible Xalan-C and Xerces-C distributions into a common directory known by the system PATH environment. You can safely merge the lib directories of Xalan-C and Xerces-C into a common directory. You can safely merge the include directories of both Xalan-C and Xerces-C as long as the subdirectories of xalanc and xercesc remain intact.

Configure Windows PATH

Windows systems require that the bin directories be added to the PATH environment so the library DLL files can be found. The Xalan.exe program is dynamically linked to these libraries.

You can make the PATH environment a permanent part of the SYSTEM or user login DESKTOP environment. Any PATH you add to the user login DESKTOP environment gets automatically prepended to the SYSTEM PATH environment and is effective upon successful user DESKTOP login. If your computer also starts Windows Services that run on behalf of a user, the user environment is assumed.

  1. Right-Click on the computer icon.
  2. Select Properties
  3. Select Advanced System Settings.
  4. SelectEnvironment Variables.
  5. Add the bin directory to the system PATH environment.

The XP, NT, 2000, and 3000 systems allow environment variables to be set explicitly to individual user accounts. The Vista, Win-7, and 2008 systems have security administration that gets in the way of updating individual user environments.

Or you can add the bin directories temporarily to your environment by program control or invoking a shell command script, or using a command window. The following command line will append your {target}/bin directory to the PATH environment.

set PATH=%PATH%;{target}/bin

(top)

Install Documentation Packages

There are actually two distributed documentation packages. One contains the website pages and full interactive apiDoc images (355+ megabytes). The other contains the website pages and the apiDoc descriptions (47 megabytes) without the apiDoc images. Except for the absence of interactive apiDoc images, the documentation packages are identical.

The documentation packages are distributed as tar and zip files. You just extract the contents into a directory that is reachable by your favorite web browser. The documentation tree starts with the ./xalan-c/ directory. The top documentation page is the ./xalan-c/index.html file.

The documentation is initially a snapshot of the Apache Xalan-C/C++ website at the time the product was released.

(top)