From: airplanemath <airplanemath@aol.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] python-imaging
Date: Thu, 9 Jul 2020 20:20:06 -0400 [thread overview]
Message-ID: <b3d1207c-52ec-144d-bff3-fcf6918c7ff3@aol.com> (raw)
In-Reply-To: <136eb766-af71-c758-186b-fd9c98214642@aol.com>
Sending to actual list this time:
On 7/8/2020 10:59 AM, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>> Hello,
>>
>> Attached is my cygport file. As usual, the test packages are available
>> at https://www.hamishmb.com/files/cygwin-temp/.
>>
>> If anyone has feedback I'd appreciate it very much.
> I tend to use loops like
>
> for ver in ${PYTHON_WHEEL_VERSIONS//:/ };
> do
> /usr/bin/python${ver} script
> done
>
> for the tests. Also, I believe ${ARCH} is the same as $(uname -m) here,
> if you want to streamline the PYTHONPATH definition a bit. Both of
> those are personal style and you are entirely welcome to ignore this.
>
> Other than that, I noticed you're writing your own src_compile and
> src_install. Is there some reason python_wheel_compile and
> python_wheel_install aren't working for you? I haven't noticed a problem
> with either of those functions in the past year or so. (For reference, the
> value of PYTHON_WHEEL_VERSIONS determines which python versions
> are compiled: see
> https://cygwin.github.io/cygport/python-wheel_cygclass.html#robo361).
>
> Thank you for taking up this package.
>
>> Hamish McIntyre-Bhatty
next prev parent reply other threads:[~2020-07-10 0:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 14:59 Hamish McIntyre-Bhatty
[not found] ` <136eb766-af71-c758-186b-fd9c98214642@aol.com>
2020-07-10 0:20 ` airplanemath [this message]
2020-07-10 10:26 ` Hamish McIntyre-Bhatty
2020-07-10 12:24 ` marco atzeri
2020-07-14 14:41 ` Hamish McIntyre-Bhatty
2020-07-17 21:03 ` Hamish McIntyre-Bhatty
2020-07-17 21:11 ` Brian Inglis
2020-07-17 21:25 ` Marco Atzeri
2020-07-18 20:07 ` Marco Atzeri
2020-07-19 16:36 ` Hamish McIntyre-Bhatty
2020-07-19 17:09 ` Marco Atzeri
2020-07-19 17:26 ` Hamish McIntyre-Bhatty
2020-07-19 19:09 ` Marco Atzeri
2020-07-21 16:04 ` Hamish McIntyre-Bhatty
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=b3d1207c-52ec-144d-bff3-fcf6918c7ff3@aol.com \
--to=airplanemath@aol.com \
--cc=cygwin-apps@cygwin.com \
/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).