Bug #4678


Automating installation of Saxon/C

Added by O'Neil Delpratt over 3 years ago. Updated about 1 year ago.

Start date:
Due date:
% Done:


Estimated time:
Found in version:
Fixed in version:


Over the years we have seen Saxon/C used in variety of platforms and environments. There are 2 stages to installation. The first stage is to install as core the saxon cross compiled library, along with the Excelsior Jet runtime to run the saxon library. The second stage is the interfacing with C++, and languages strongly coupled with C++ such as PHP or Python extension libraries. The second stage is well automated but the first stage is somewhat a manual process and may involve some handwaving in places.

It would be helpful if we could automate the installation process of the first stage: the Excelsior Jet runtime and the cross compiled Saxon library as described here: installing and specifically for Linux and MacOS.

This automation process should be implemented as a bash shell script, which should do the following:

  1. Put required libraries (i.e. rt directory, libsaxon[EDITION].so and saxon-data directory) in the desired location or default if not specified (e.g. /usr/lib for linux).

  2. set the SAXONC_HOME environment accordingly from 1.

  3. Any other useful setups such as building samples, etc.

Actions #1

Updated by O'Neil Delpratt over 3 years ago

Useful post on the best location to install Saxon/C as default: /opt vs /usr/lib vs /usr/local/lib

Actions #2

Updated by O'Neil Delpratt about 1 year ago

  • Status changed from New to Closed
  • Fixed in version set to 12.0

We have made good progress on the installation process in SaxonC 12 for example we now have Python package wheels for installing SaxonC for Python. We have moved on from Excelsior Jet to use Graalvm which only has one library file.

I am closing this bug issue.

Please register to edit this issue

Also available in: Atom PDF