Bug #6299
open
Add a Makefile to the release for building of the SaxonC C/C++ API library
0%
Description
Reported by user here https://stackoverflow.com/questions/77684816/undefined-reference-error-when-link-to-saxon-library-in-c/77690492#77690492
The SaxonC release should contain a MakeFile to build the C/C++ library. This is something we attempted to do long time ago, but for some reason we proceed with its use. Since we are now using Graalvm we should use a Makefile.
Updated by Norm Tovey-Walsh 12 months ago
Yes, definitely. I assumed we were avoiding it because of Windows build problems. But if that's not the case, it would be better and simpler than shell scripts, I think.
Updated by O'Neil Delpratt 5 days ago
- Assignee changed from O'Neil Delpratt to Matt Patterson
Updated by Matt Patterson 5 days ago
We've been experimenting with using CMake to generate a build system for SaxonC, and that has been very promising. There are a couple of open questions about how to consume SaxonC as a library, and there are implications for how we build SaxonC Python and PHP that still need shaking out before we can make this publicly available.
We also need to test that our release artifacts can be successfully imported into a CMake-using client project. In theory this also gives us options for easily generating pkg-config .pc files as well. One or both of these hopefully address issues like the one raised in #1962.
Please register to edit this issue
.