From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 45550 invoked by alias); 11 Jul 2017 14:37:53 -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 44042 invoked by uid 89); 11 Jul 2017 14:37:52 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=ham version=3.3.2 spammy=personal, HContent-Transfer-Encoding:8bit X-HELO: mail-it0-f50.google.com Received: from mail-it0-f50.google.com (HELO mail-it0-f50.google.com) (209.85.214.50) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 11 Jul 2017 14:37:51 +0000 Received: by mail-it0-f50.google.com with SMTP id m68so65322076ith.1 for ; Tue, 11 Jul 2017 07:37:51 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=UOcWvybDbfvr6nZfP1uJiszIEK7ifdMCUiBGClYA3Pg=; b=jNLgsSlOgU9zMJkNeJ48i5o88Gx/Ogmw1JSdx3qMaFlzegn06OMuyqCEv3vSv160qK G7jYP2lGfh7bzmYyll4FclK/hdkWsw0XmNnXOfAp88ai4sevske316aMrF9ftarMt/EQ d1y2WZY1yp9HdBhPFDmHjmuYSlLJlKoLeQq7GOiGT0Vc6S/UFj2Wa2W5LFsCNWWQuxOl 621FIdl77WxRIoR5S6BZgbUMuChXFQeDFbYg0b3xrbWt6YVIEx/zNm2u7pfTg90Api3K /m6+GiRNf55GaXJ06FsJ+uT4Mu+Ig/46pNQKfu/4VdlQhG2W5epdpJFk6GsBgG2KKMWG Oe5g== X-Gm-Message-State: AIVw1123R/Dzt3i2jqxRRWxWAGQdVGsRxTloPuVfiz40QdCO6wz6V7e1 zZqR5K6VvK+83No6 X-Received: by 10.36.112.82 with SMTP id f79mr16985004itc.65.1499783869550; Tue, 11 Jul 2017 07:37:49 -0700 (PDT) Received: from [192.168.0.6] (d4-50-42-50.try.wideopenwest.com. [50.4.50.42]) by smtp.gmail.com with ESMTPSA id h29sm5373017iti.28.2017.07.11.07.37.48 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Jul 2017 07:37:48 -0700 (PDT) Subject: Re: distinguishing cygwin from mingw binaries To: cygwin@cygwin.com References: From: cyg Simple Message-ID: <728bfde3-3608-3a81-131e-f012aaa6cdce@gmail.com> Date: Tue, 11 Jul 2017 14:37: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 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2017-07/txt/msg00185.txt.bz2 On 7/10/2017 1:40 PM, Nellis, Kenneth wrote: > 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 > > Curious what techniques others might use. > I would use a --prefix or whatever defines the install directories in your cases to be something easily recognizable and install it. Then execute a recursive grep on that folder. grep -lir --binary-files=binary cygwin1.dll /my/install/dir If a file is listed then you can decide what to do next. -- cyg Simple -- 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