From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] python36-wx 4.0.7.post2
Date: Thu, 11 Jun 2020 17:19:49 +0200 [thread overview]
Message-ID: <14fef64e-0fa5-1c78-e355-7f2e934c4c32@gmail.com> (raw)
In-Reply-To: <AM0PR05MB48980B0885A90984FA263AB3E7830@AM0PR05MB4898.eurprd05.prod.outlook.com>
On 10.06.2020 11:34, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> 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.
on python 3.8 they should be
-lpython3.8 and python3.8
You can use pkconfig to recover it
$ pkg-config --libs python-3.8
-lpython3.8
$ pkg-config --libs python-3.7
-lpython3.7m
next prev parent reply other threads:[~2020-06-11 15:19 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
2020-06-11 15:19 ` Marco Atzeri [this message]
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=14fef64e-0fa5-1c78-e355-7f2e934c4c32@gmail.com \
--to=marco.atzeri@gmail.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).