From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: distinguishing cygwin from mingw binaries
Date: Mon, 10 Jul 2017 19:01:00 -0000 [thread overview]
Message-ID: <c9972edc-e767-c692-ce3f-9d577ddfc130@t-online.de> (raw)
In-Reply-To: <BN6PR2001MB1074F351B65B71F7B8B41143F1A90@BN6PR2001MB1074.namprd20.prod.outlook.com>
Am 10.07.2017 um 19:40 schrieb Nellis, Kenneth:
> For my personal use, I use gcc to generate binaries, but occasionally I need
> to make a binary available to someone who doesn't use Cygwin. For that I use
> Cygwin's x86_64-w64-mingw32-gcc.
>
> After the fact, I would like to know whether the binary requires Cygwin support
> or not. One way is: strings foo.exe | grep cygwin1.dll
That's a bit too rough. Something like
cygcheck ./foo.exe | grep cygwin1.dll
or ldd ./foo.exe | grep cygwin1.dll
would be more precise.
> One of my wishes for Cygwin is for the "file" command to make the distinction.
Well, SHTDI. IOW: please don't feel as if anybody were keeping you from
constructing a 'file' rule that achieves that, and offering it to the
public. ;-)
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-07-10 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 17:40 Nellis, Kenneth
2017-07-10 19:01 ` Hans-Bernhard Bröker [this message]
2017-07-11 14:20 ` Nellis, Kenneth
2017-07-11 14:37 ` cyg Simple
2017-07-10 18:01 Kaz Kylheku
2017-07-11 14:43 ` cyg Simple
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=c9972edc-e767-c692-ce3f-9d577ddfc130@t-online.de \
--to=hbbroeker@t-online.de \
--cc=cygwin@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).