Actions
Bug #4609
open![Author: O'Neil Delpratt](https://www.gravatar.com/avatar/a0bc1766b412d8fecb16f7d304916359?rating=PG&size=50&default=https%3A%2F%2Fassets.plan.io%2Fimages%2Fdefault_avatar.png)
![Assignee: Matt Patterson](https://www.gravatar.com/avatar/21bf065778960e144848711e16058496?rating=PG&size=22&default=https%3A%2F%2Fassets.plan.io%2Fimages%2Fdefault_avatar.png)
Lack of documentation to package Saxon/C C++ in third-party systems
Start date:
2020-06-22
Due date:
% Done:
0%
Estimated time:
Applies to branch:
Fix Committed on Branch:
Fixed in Maintenance Release:
Found in version:
1.2.1
Fixed in version:
SaxonC Languages:
SaxonC Platforms:
SaxonC Architecture:
Description
This bug is created as a result of a user enquiry.
There seems to be a lack of documentation on how to package Saxon/C C++ API in a third-party system. There needs to be a clear guide to say what needs building in advance to create the required executable files for another system within the C++ environment (i.e. modules/dlls/components for Saxon/C runtime?)
Updated by O'Neil Delpratt 3 months ago
- Assignee changed from O'Neil Delpratt to Matt Patterson
Please register to edit this issue
Actions