X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=aEInrYzNUWUEK5oU
	BFowFGKXmCd0fZFAs8fnvTaBuDMDFmK9x5ZsNEzSJ8eladN/JwquFO0ar1lYNuzF
	CLPWcLZC0ne7KjWzT5fmr1cwAqsDMQ5ED0REGNCzPBMfu4RJhsG5RKUCNfuJTIyE
	FMeXaC1iIL0wn6+fukrBVSA8k6A=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=+DWCgAEnjZBk4dkNTWfj6f
	Tzhso=; b=RudXIHWFxaWyuEUusTOsfvlNo7CKQhCj28q+NWTZPkAoNbruXUkSUS
	O06wqF2WyxTaYg6+BGlsnMb1rhquCRwloF4euYrYWABGw5zZOKn2oDJhTzmCbRqi
	u1/kKFwq7Qr/4Vpayqw+nuTTHJxpPeJa3GN/9uAfwAgxt5L024SbY=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-0.8 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=Hx-languages-length:806, H*F:D*t-online.de, wishes, personal
X-HELO: mailout09.t-online.de
Subject: Re: distinguishing cygwin from mingw binaries
To: cygwin AT cygwin DOT com
References: <BN6PR2001MB1074F351B65B71F7B8B41143F1A90 AT BN6PR2001MB1074 DOT namprd20 DOT prod DOT outlook DOT com>
From: =?UTF-8?Q?Hans-Bernhard_Br=c3=b6ker?= <HBBroeker AT t-online DOT de>
Message-ID: <c9972edc-e767-c692-ce3f-9d577ddfc130@t-online.de>
Date: Mon, 10 Jul 2017 21:01:08 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <BN6PR2001MB1074F351B65B71F7B8B41143F1A90@BN6PR2001MB1074.namprd20.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

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