From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5168 invoked by alias); 10 Jul 2017 19:01:21 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 5160 invoked by uid 89); 10 Jul 2017 19:01:21 -0000 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 Received: from mailout09.t-online.de (HELO mailout09.t-online.de) (194.25.134.84) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 10 Jul 2017 19:01:19 +0000 Received: from fwd41.aul.t-online.de (fwd41.aul.t-online.de [172.20.27.139]) by mailout09.t-online.de (Postfix) with SMTP id 5A215424F65C for ; Mon, 10 Jul 2017 21:01:17 +0200 (CEST) Received: from [192.168.2.28] (Xjj5A4ZZwhgDirkYPiLD3urXGZuwIY5Kfuu6suk6vVONMbN6akcyAoF0mj4b3awgWz@[91.59.12.3]) by fwd41.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1dUdvk-1XZJr60; Mon, 10 Jul 2017 21:01:12 +0200 Subject: Re: distinguishing cygwin from mingw binaries To: cygwin@cygwin.com References: From: =?UTF-8?Q?Hans-Bernhard_Br=c3=b6ker?= Message-ID: Date: Mon, 10 Jul 2017 19:01:00 -0000 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: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2017-07/txt/msg00147.txt.bz2 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