public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Python Packages
Date: Thu, 30 Jul 2020 18:59:16 +0200	[thread overview]
Message-ID: <36241af8-23dd-cc0c-3b40-d3b404668fa4@gmail.com> (raw)
In-Reply-To: <MN2PR17MB3999F095F6698F32646866AFB8710@MN2PR17MB3999.namprd17.prod.outlook.com>

On 30.07.2020 09:25, Allen Hewes via Cygwin wrote:
>>> I have a few Python packages built (and very minor change) for Python 3.8,
>> but before I follow the directions for package contributions, I have a few
>> questions:
>>>

> 
> I think there's a few which have C interfaces. I didn't check nor am I familiar enough with Cygwin, are no-arch dirs being used for libs? I am pretty sure DLLs were built. 
> Can someone have multi-lib/multi-arch Pythons installed in Cygwin? I've only ever used a single arch myself.


if there are dlls than you need to build 32 and 64 version

otherwise if they just contains *py and *pyc they are noarch

$ cygport python-cffi.cygport list | grep dll
/usr/lib/python2.7/site-packages/_cffi_backend.dll
/usr/lib/python3.6/site-packages/_cffi_backend.cpython-36m-x86_64-cygwin.dll
/usr/lib/python3.7/site-packages/_cffi_backend.cpython-37m-x86_64-cygwin.dll
/usr/lib/python3.8/site-packages/_cffi_backend.cpython-38-x86_64-cygwin.dll



Regards
Marco



  reply	other threads:[~2020-07-30 16:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-30  4:57 Allen Hewes
2020-07-30  6:15 ` Marco Atzeri
2020-07-30  7:25   ` Allen Hewes
2020-07-30 16:59     ` Marco Atzeri [this message]
2020-08-12  6:58 ` Marco Atzeri
2020-08-13 14:13   ` Allen Hewes

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=36241af8-23dd-cc0c-3b40-d3b404668fa4@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@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).