Project

Profile

Help

Bug #4595

closed

commands library paths not customizable

Added by O'Neil Delpratt about 4 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Category:
Saxon-C Internals
Start date:
2020-06-16
Due date:
% Done:

100%

Estimated time:
Found in version:
1.2.1
Fixed in version:
11.1
Platforms:

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

Validate.c (10.5 KB) Validate.c O'Neil Delpratt, 2020-06-16 11:47
Query.c (10.6 KB) Query.c O'Neil Delpratt, 2020-06-16 11:47
Transform.c (10.6 KB) Transform.c O'Neil Delpratt, 2020-06-16 11:47

Related issues

Related to SaxonC - Bug #4594: build file for command interface not available on WindowsClosedO'Neil Delpratt2020-06-15

Actions

Please register to edit this issue

Also available in: Atom PDF