public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jim Garrison <jhg@jhmg.net>
To: cygwin@cygwin.com
Subject: Trying to build OCRmyPDF under Cygwin, hit a brick wall
Date: Thu, 14 May 2020 12:45:00 -0700	[thread overview]
Message-ID: <a5987f7c-1448-ce81-d40b-e3034e406eb8@jhmg.net> (raw)

I'm trying to build OCRmyPDF under Cygwin and have run into a brick
wall. While I've been a developer my entire career, I've worked mostly
in Java and have little knowledge of Python internals and C++. The
problem might be obvious to an expert in these areas but I'm stumped.

OCRmyPDF on Linux installs as a set of "wheel" packages. I gather a
wheel is a pre-built bundle of dependencies. For some reason, under
Cygwin the pip installer believes it cannot use the wheel bundles and
wants to rebuild from source. The problem occurs when trying to rebuild
the pikepdf package.

This post is preliminary. Including the error message here would be
hard to read as it contains very long lines that will wrap and
alignment will be messed up.  I've posted the question to StackOverflow
at https://stackoverflow.com/q/61803714/18157 where I can use markdown
to make it much more readable.

Is it OK to ask here for any interested party to look at the SO post?
If not, I apologize, and I will post the question in its entirety
here.

Thanks

-- 
Jim Garrison jhg@acm.org

             reply	other threads:[~2020-05-14 19:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-14 19:45 Jim Garrison [this message]
2020-05-14 22:50 ` Jim Garrison
2020-05-15  0:23   ` René Berber
2020-05-15 18:17     ` Jim Garrison
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=a5987f7c-1448-ce81-d40b-e3034e406eb8@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).