Hello, AFAICT the `rpath` setting is only functional during the linking phase but not in the runtime, thus it won't really work as you expected.
The proper solution would be, as JB indicates, to build a dynamically-linked Tesseract, and use the LD_LIBRARY_PATH environment variable to make the dynamic linker load the depending libraries from the right paths. I'm actually building a Tesseract distribution that ships a launcher that'll automatically done this, however it isn't released yet. Cheers, 林博仁(Buo-ren, Lin) [email protected] -- You received this message because you are subscribed to the Google Groups "tesseract-ocr" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tesseract-ocr/7518be91-d493-4292-ad83-8598de1c23a8%40googlegroups.com.
