public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: Cygwin Patches <cygwin-patches@cygwin.com>
Subject: Re: [PATCH] winsup/doc/dll.xml: update MinGW/.org to MinGW-w64/.org
Date: Sun, 7 Mar 2021 13:26:28 -0700	[thread overview]
Message-ID: <38792da7-75f7-231d-0de2-d483b927820a@SystematicSw.ab.ca> (raw)
In-Reply-To: <aada0b19-26ea-9db0-85f4-8f959441e05a@dronecode.org.uk>

On 2021-03-07 12:15, Jon Turney wrote:
> On 07/03/2021 16:31, Brian Inglis wrote:
>> ---
>>   winsup/doc/dll.xml | 5 +++--
>>   1 file changed, 3 insertions(+), 2 deletions(-)

> I don't think the link here actually has much value, and would be inclined to 
> drop it, as far as I can tell it's just giving that as an example of a toolchain 
> which produces 'lib'-prefixed DLLs.
> 
> Also, reading the whole page, the section "Linking against DLLs" needs updating 
> since GNU ld has had the ability to link directly against DLLs (automatically 
> generating the necessary import stubs) for a number of years.
> 
> Also, there are other mentions of MinGW.org on the cygwin website (e.g. 
> https://cygwin.com/links.html) which also need updating, if that URL is no 
> longer valid.

I checked the tree and Corinna cleaned up some a few years ago.

I already checked winsup/doc/ and there were no other substantive uses of MinGW 
unless you would prefer *ALL* mentions of MinGW be suffixed with -w64.

I did not look closely at cygwin-htdocs, as git complained when I tried to 
update, so I wiped that repo, but it looks like links.html and categories in 
packaging-hint-files.html which includes Mingw, needed updated.

Is there a definitive file with a list of all currently valid categories in 
calm, cygport, setup, or shared somewhere?
I may get to reclone, check, and patch htdocs later.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

  reply	other threads:[~2021-03-07 20:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-07 16:31 Brian Inglis
2021-03-07 19:15 ` Jon Turney
2021-03-07 20:26   ` Brian Inglis [this message]
2021-03-08 10:14     ` Corinna Vinschen
2021-03-08 17:32       ` Brian Inglis
2021-03-08 17:38         ` Achim Gratz
2021-03-08 18:19           ` Brian Inglis
2021-03-08 19:09             ` Achim Gratz
2021-03-08 20:20               ` Ken Brown
2021-03-08 20:52                 ` ASSI
2021-03-08 20:55                 ` Corinna Vinschen
2021-03-09  6:08                   ` Brian Inglis
2021-03-08 10:13   ` Corinna Vinschen

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=38792da7-75f7-231d-0de2-d483b927820a@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin-patches@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).