public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH] winsup/doc/dll.xml: update MinGW/.org to MinGW-w64/.org
Date: Mon, 8 Mar 2021 11:13:28 +0100	[thread overview]
Message-ID: <YEX4yHo5zbjPx9x9@calimero.vinschen.de> (raw)
In-Reply-To: <aada0b19-26ea-9db0-85f4-8f959441e05a@dronecode.org.uk>

On Mar  7 19: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.

However, telling people we use cyg instead of lib for $reason, and then
not pointing to at least one project using this prefix seems puzzeling.
Given that Windows doesn't use a prefix at all, the URL to mingw-w64
might help, doesn't it?

> 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.

What do you suggest?  Shall we just remove the section entirely?

> 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.

Yeah, we should remove them or move them to mingw-w64, too.


Thanks,
Corinna

      parent reply	other threads:[~2021-03-08 10:13 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
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 [this message]

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=YEX4yHo5zbjPx9x9@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --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).