From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] python36-wx 4.0.7.post2
Date: Wed, 10 Jun 2020 10:34:36 +0100 [thread overview]
Message-ID: <AM0PR05MB48980B0885A90984FA263AB3E7830@AM0PR05MB4898.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <2b10fc1f-26e0-6507-2c2c-7330d1dd4f6d@gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1877 bytes --]
On 09/06/2020 20:53, Marco Atzeri via Cygwin-apps wrote:
>
> It is probably possible to build
>
> python36-wx and python37-wx together with the same source package.
> The only files of the binaries they seem to share are
>
> usr/share/icons/hicolor/16x16/apps/PyCrust.png
> usr/share/icons/hicolor/32x32/apps/PyCrust.png
>
> that can be put in a tiny shared common subpackage
>
Seems like a good idea, I'll do that.
> python38-wx will need python38-numpy that is not yet available.
>
Yeah. There's also a problem with the dev package I think, because
-lpython3.8m can't find the library, and python3.8m doesn't seem to
exist as a command. I might just be being a doofus though so I'll double
check that I installed the right packages.
> Maybe it is also possible to build python27-wx, but I doubt is is worth
> the effort as we should move faster on python3.8
>
Yeah, I was more concerned about getting a really well-working wxPython
3.0 build for Python 2. Also I think the combo of wxPython 4 and Python
2 is probably uncommon so yeah I agree, better off focusing on Python 3.8.
My only question is that PYTHON3_SITELIB seems to only point to 3.6's
site packages folder. Any way I can override this or should I just
hardcode "/usr/lib/python3.7/site-packages" in my cygport file?
> Questions:
> - why 4.0.7.post2 and not 4.1.0 ?
Because 4.1.0 requires wxWidgets 3.1.x, which is not currently in
Cygwin, and I have used wxPython 4.0.x a lot and can verify that it
works well.
Having said that, I fully intend to update it to wxPython 4.1.x sometime
soon, it's just that 4.0.x is what I've spent ages debugging so I'd like
to get a working build out for that first.
> - have you a BUILD_REQUIRES list ?
> just to avoid a try loop to test my idea
>
Actually no but that's a good idea. I'll do that too.
Thanks,
Hamish
[-- Attachment #1.1.2: 0x87B761FE07F548D6.asc --]
[-- Type: application/pgp-keys, Size: 3235 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-06-10 9:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 16:52 Hamish McIntyre-Bhatty
2020-06-09 19:53 ` Marco Atzeri
2020-06-10 9:34 ` Hamish McIntyre-Bhatty [this message]
2020-06-11 15:19 ` Marco Atzeri
2020-06-11 16:03 ` Hamish McIntyre-Bhatty
2020-06-11 16:41 ` Marco Atzeri
2020-06-15 10:20 ` Hamish McIntyre-Bhatty
2020-06-15 18:26 ` Achim Gratz
2020-06-17 8:41 ` Hamish McIntyre-Bhatty
2020-06-17 19:24 ` Marco Atzeri
2020-06-17 21:23 ` Hamish McIntyre-Bhatty
2020-06-18 8:20 ` Hamish McIntyre-Bhatty
2020-06-18 9:24 ` Marco Atzeri
2020-06-18 11:31 ` Hamish McIntyre-Bhatty
2020-06-18 14:08 ` Jon Turney
2020-06-18 15:05 ` 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=AM0PR05MB48980B0885A90984FA263AB3E7830@AM0PR05MB4898.eurprd05.prod.outlook.com \
--to=hamishmb@live.co.uk \
--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).