From: Jim Garrison <jhg@jhmg.net>
To: cygwin@cygwin.com
Subject: Re: Trying to build OCRmyPDF under Cygwin, hit a brick wall
Date: Fri, 15 May 2020 11:17:35 -0700 [thread overview]
Message-ID: <514bbf03-b259-bd98-c06c-38a794e5b0af@jhmg.net> (raw)
In-Reply-To: <d4070d22-4298-9ee7-bc31-202cb107caf6@gmail.com>
On 5/14/2020 5:23 PM, René Berber via Cygwin wrote:
[snip]
>> if os.name == 'nt':
>> libname = 'liblept-5'
>> os.environ['PATH'] = shim_paths_with_program_files()
>
> Notice this change in search path, dll files in Windows are executables
> and they are (must) installed in the system PATH (or the current
> directory).
$PATH contains /usr/bin
> Either that or python needs the symbols file, like the linker, which in
> this case would be /usr/lib/liblept.dll.a, which is in the -devel
> package, but I doubt it.
Installing the -devel package, and undoing my "fix" to leptonica.py
fixed the problem. I guess I'm now going to have to learn how to
build a Cygwin package for it.
Unfortunately I didn't realize how involved building it on Cygwin was
going to be and that it would be worth documenting, so I didn't keep
track of everything I had to do (sigh!)
How would I gauge interest in having a Cygwin version of OCRmyPDF?
--
Jim Garrison jhg@acm.org
next prev parent reply other threads:[~2020-05-15 18:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 19:45 Jim Garrison
2020-05-14 22:50 ` Jim Garrison
2020-05-15 0:23 ` René Berber
2020-05-15 18:17 ` Jim Garrison [this message]
2020-05-15 1:45 ` Marco Atzeri
2020-05-15 18:19 ` Jim Garrison
[not found] <0d9b4a1b-05ba-8ab1-3783-c3d1f04f97b7@gmail.com>
2020-05-15 19:34 ` Marco Atzeri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=514bbf03-b259-bd98-c06c-38a794e5b0af@jhmg.net \
--to=jhg@jhmg.net \
--cc=cygwin@cygwin.com \
--cc=jhg@acm.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).