From: JonY <10walls@gmail.com>
To: Boris Kolpackov <boris@codesynthesis.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PING] Plugin support on Windows/MinGW
Date: Sun, 26 Nov 2017 20:01:00 -0000 [thread overview]
Message-ID: <791f23af-555e-3ead-2db7-52a4c61cf456@gmail.com> (raw)
In-Reply-To: <be29e565-f7b8-07f0-cc70-e0929276d5df@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1055 bytes --]
On 11/23/2017 11:34 AM, JonY wrote:
> On 11/22/2017 11:14 AM, Boris Kolpackov wrote:
>> JonY <10walls@gmail.com> writes:
>>
>>> Is there a problem with using .so for internal libraries instead of
>>> "dll"...
>>
>> I think not but I haven't tested it. The problem with using .so instead
>> of .dll is that producing this non-standard extension may not be easy
>> or possible depending on the build system/tool (e.g., libtool). Also,
>> you never know how other pieces of the system (like antivirus) will
>> react to a file that looks like a DLL but is called something else.
>>
>>
>
> Libtool shouldn't matter since it is not used to build those, and I
> doubt AVs would care what the filename is called. Apache on Windows uses
> .so plugins too.
>
>>> ... if it simplifies the code?
>>
>> I don't think it simplifies that much and the potential (and unknown)
>> downside is significant.
>>
>> Thanks for the review,
>> Boris
>>
>
> I'll commit in a few days if there are no more inputs.
>
Applied to trunk r255154.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 858 bytes --]
prev parent reply other threads:[~2017-11-26 13:05 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
2017-11-26 20:01 ` JonY [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=791f23af-555e-3ead-2db7-52a4c61cf456@gmail.com \
--to=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).