This is the mail archive of the
mailing list for the Cygwin project.
distinguishing cygwin from mingw binaries
- From: "Nellis, Kenneth" <Kenneth dot Nellis at conduent dot com>
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Mon, 10 Jul 2017 17:40:31 +0000
- Subject: distinguishing cygwin from mingw binaries
- Authentication-results: sourceware.org; auth=none
- Authentication-results: cygwin.com; dkim=none (message not signed) header.d=none;cygwin.com; dmarc=none action=none header.from=conduent.com;
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
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
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.
One of my wishes for Cygwin is for the "file" command to make the distinction.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple