Lack of documentation to package Saxon/C C++ in third-party systems
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?)
Please register to edit this issue