Actions
Bug #4595
closedcommands library paths not customizable
Start date:
2020-06-16
Due date:
% Done:
100%
Estimated time:
Applies to branch:
Fix Committed on Branch:
Fixed in Maintenance Release:
Found in version:
1.2.1
Fixed in version:
11.1
SaxonC Languages:
SaxonC Platforms:
SaxonC Architecture:
Description
From the resolution of the bug issue #4594 I discovered that from the Saxon/C command-line interfaces there is no way to customize the location of the Saxon/C library from the defaults.
I have copied the same logic of the code in the C++ API from the file SaxonCGlue.c which allows users to set the environmental variable SAXONC_HOME
.
Files
Related issues
Please register to edit this issue
Actions