From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Cygport user guide
Date: Tue, 9 Jun 2020 14:23:29 +0100 [thread overview]
Message-ID: <AM0PR05MB4898BA4F888EF5F813052226E7820@AM0PR05MB4898.eurprd05.prod.outlook.com> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 339 bytes --]
In the process of making my cygport file for wxPython 4, I've quite
quickly found that I don't understand how cygport works all that well.
The reference guide is extremely useful, but it's a bit tricky finding
which things are useful/relevant. Is there a user guide for
Cygport/could we make one (I'd be happy to help)?
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 reply other threads:[~2020-06-09 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 13:23 Hamish McIntyre-Bhatty [this message]
2020-06-09 15:55 ` marco atzeri
2020-06-09 16:54 ` Hamish McIntyre-Bhatty
2020-06-09 22:49 ` Doug Henderson
2020-06-12 14:44 ` Jon Turney
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=AM0PR05MB4898BA4F888EF5F813052226E7820@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).