From: Orgad Shaneh <orgads@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Support MSYS platform
Date: Sun, 3 Mar 2024 13:04:10 +0200 [thread overview]
Message-ID: <CAGHpTBLc_wBtx8GdY866tdxbWBr4PW6Bt8zR9G-zNoXM==0j8A@mail.gmail.com> (raw)
In-Reply-To: <86h6hnoa5o.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
On Sun, Mar 3, 2024 at 12:57 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Orgad Shaneh <orgads@gmail.com>
> > Date: Sun, 3 Mar 2024 11:46:53 +0200
> > Cc: gdb-patches@sourceware.org
> >
> > But before that: what exactly is the MSYS target, and how does it
> > differ from MinGW and Cygwin targets?
> >
> > See https://www.msys2.org/docs/what-is-msys2/
> >
> > It is based on Cygwin, but focuses on support for native Windows apps.
> >
> > It also features a decent package manager, which Cygwin doesn't.
>
> I was asking what is the native debugging target for this build. I'm
> guessing those are MSYS2 (as opposed to MinGW64) programs, is that
> right? Because if you say "support for native Windows apps", then it
> is not clear how is this different from the MinGW port of GDB, which
> also targets native Windows programs.
>
The runtime dlls are different, and the build environment is different
(uname -s: MSYS_NT-10.0-19043)
- Orgad
next prev parent reply other threads:[~2024-03-03 11:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-03 7:58 Orgad Shaneh
2024-03-03 8:56 ` Eli Zaretskii
2024-03-03 9:46 ` Orgad Shaneh
2024-03-03 10:57 ` Eli Zaretskii
2024-03-03 11:04 ` Orgad Shaneh [this message]
2024-03-03 9:43 ` [PATCH] Support MSYS2 platform Orgad Shaneh
2024-03-03 10:54 ` Eli Zaretskii
2024-03-03 11:06 ` Orgad Shaneh
2024-03-03 11:07 ` Orgad Shaneh
2024-03-08 17:36 ` Tom Tromey
2024-03-08 19:41 ` Eli Zaretskii
2024-03-09 20:47 ` Orgad Shaneh
2024-03-10 14:27 ` Tom Tromey
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='CAGHpTBLc_wBtx8GdY866tdxbWBr4PW6Bt8zR9G-zNoXM==0j8A@mail.gmail.com' \
--to=orgads@gmail.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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).