Summary: | Allow to build OCR devices against system tesseract and leptonica | ||
---|---|---|---|
Product: | GhostPDL | Reporter: | M.J.G. <mjg> |
Component: | Build Process | Assignee: | Robin Watts <robin.watts> |
Status: | RESOLVED DUPLICATE | ||
Severity: | enhancement | CC: | carlo.antonio.cabrera, chris.liddell, sam |
Priority: | P4 | ||
Version: | master | ||
Hardware: | PC | ||
OS: | Linux | ||
Customer: | Word Size: | --- |
Description
M.J.G.
2022-08-19 15:05:42 UTC
We'd appreciate this at Homebrew too. We currently carry a patch [1] to fix some macOS builds of your bundled leptonica. It would really be much better if we only needed to patch leptonica in one place instead of multiple ones. See discussion at [2]. Arch users would likely benefit from this too, as installing ghoscript using pacman results in an installation that lacks OCR support. [3] Allowing the use of system libraries would likely have Arch building with this feature enabled when they link with system versions of tesseract and leptonica. [1] https://github.com/Homebrew/homebrew-core/blob/c266044e8e4319eb214efc08a8d2235b11bb7d1a/Formula/ghostscript.rb#L61-L69 [2] https://github.com/Homebrew/homebrew-core/pull/111494 [3] https://github.com/archlinux/svntogit-packages/blob/24a8a17317635b9d45551e4e7322edf14c8346b0/trunk/PKGBUILD#L34-L41 FYI, I recently built ghostscript for Fedora rawhide (development version) against system tesseract and leptonica (just as a test build), and ocr devices showed up, and a minimal example works. Is it safe to assume that we can use this in distro builds now? By that I mean that the build scripts will continue supporting this? I don't expect support for broken distro builds, of course. In case of problems we'd have to check against standard builds with bundled libs. Yes, we'll support this moving forwards. The only thing I ought to add are versions checks for tesseract and leptonica. But since the current code should cope with tesseract 4 and 5, which I think are the only mainstream versions just now. *** This bug has been marked as a duplicate of bug 706490 *** |