Bug #4524
closed
Saxon/C documentation does not give information on customizing installation directory
100%
Description
Reported by user.
Per the instruction on Linux, we need to copy library files to or create symlinks in /usr/lib. Is this “/usr/lib” path hard coded? We will run our application on hundreds of farm machines. It’s not practical to ask systems to set up /usr/lib for us.
[cppTests]$ ./testXPath Unable to load /usr/lib/libsaxonhec.so Error: : Success
Is there a way to replace the path /usr/lib with our customized directory?
Updated by O'Neil Delpratt over 4 years ago
For Linux you can use the environment variable SAXONC_HOME to set the location of the Saxon/C library.
You can set it as follows:
export SAXONC_HOME=/USER/LOCATION
You may also need to set the LD_LIBRARY_PATH.
You can do it as follows:
export JET_HOME=/USER/LOCATION export LD_LIBRARY_PATH=$JET_HOME/lib/amd64/jetvm:$JET_HOME/lib/amd64:$JET_HOME
We mention this option under the Mac OS instructions Mac OS, but not under linux.
This is a bug against the Saxon/C documentation which needs to reflect details in the Linux instructions too.
Just to add, the logic for finding the Saxon/C library location is in the SaxonCGlue.c file.
Updated by O'Neil Delpratt over 4 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Saxon/C documentation updated on live site and in repositiory.
Updated by O'Neil Delpratt almost 3 years ago
- Status changed from Resolved to Closed
- Fixed in version set to 11.1
Bug fix patched in SaxonC 11.1 release
Please register to edit this issue
.