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
Updated by O'Neil Delpratt over 4 years ago
- Related to Bug #4594: build file for command interface not available on Windows added
Updated by O'Neil Delpratt over 4 years ago
- File Validate.c Validate.c added
- File Query.c Query.c added
- File Transform.c Transform.c added
- Status changed from New to Resolved
Bug fixed and committed to subversion available for the next release. I have also attached the files: Transform.c, Query.c and Validate.c for users to pick up the patch in their current Saxon/C installation.
Updated by O'Neil Delpratt almost 3 years ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in version set to 11.1
Bug fix patched in SaxonC 11.1 release
Please register to edit this issue
Actions