public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Boris Kolpackov <boris@codesynthesis.com>, JonY <10walls@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PING] Plugin support on Windows/MinGW
Date: Thu, 23 Nov 2017 12:49:00 -0000	[thread overview]
Message-ID: <574ab73e-ab6a-e954-f609-e4a34612a1a0@redhat.com> (raw)
In-Reply-To: <boris.20171123140256@codesynthesis.com>

On 11/23/2017 12:06 PM, Boris Kolpackov wrote:
> JonY <10walls@gmail.com> writes:
> 
>> Libtool shouldn't matter since it is not used to build those, [...]
> 
> We don't know which build system the plugin author will use to build
> the plugin. We can, however, reasonably expect that it will be able
> to produce a shared library with the platform-standard extensions
> (.dll, .dylib, etc).
> 
> 
>> I'll commit in a few days if there are no more inputs.
> 
> Great, thanks!

I would just like to say that I think this is a fantastic patch
that will help open GCC to many more use cases.  The fact that
plugins don't work on Windows has been a sore spot, IMO.

I for one am very happy that this make gdb's libcc1 plugin
a viable option for Windows.  Puts us one step closer to the
long term plan of making GDB always use GCC for C/C++
expression parsing/evaluation.  Yay.  :-)

Thanks,
Pedro Alves

  reply	other threads:[~2017-11-23 12:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21  7:44 Boris Kolpackov
2017-11-22 10:37 ` JonY
2017-11-22 11:25   ` Boris Kolpackov
2017-11-23 11:48     ` JonY
2017-11-23 12:20       ` Boris Kolpackov
2017-11-23 12:49         ` Pedro Alves [this message]
2017-11-26 20:01       ` JonY

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=574ab73e-ab6a-e954-f609-e4a34612a1a0@redhat.com \
    --to=palves@redhat.com \
    --cc=10walls@gmail.com \
    --cc=boris@codesynthesis.com \
    --cc=gcc-patches@gcc.gnu.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).