From: Kaz Kylheku <920-082-4242@kylheku.com>
To: cygwin@cygwin.com
Subject: Re: distinguishing cygwin from mingw binaries
Date: Mon, 10 Jul 2017 18:01:00 -0000 [thread overview]
Message-ID: <b133682e5719c0e2a546b4968a0c7233@mail.kylheku.com> (raw)
On 10.07.2017 10:40, 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.
There is always the technique of actually packaging the program
deliverables
and then testing them, beginning with installation, if you were the
end-user.
If the program doesn't run when installed by itself in C:\Program Files
somewhere, then it might be missing DLLs.
I use a special fork of Cygwin called Cygnal for delivering programs to
users who don't use Cygwin and don't understand POSIX conventions for
paths
and other things.
http://www.kylheku.com/cygnal/
With this, you make your executable with the regular Cygwin host
compiler.
Yes, you know your executable needs a CYGWIN1.DLL (and possibly others);
no guesswork. You package the needed DLL's with the program.
Except, you use the CYGWIN1.DLL from the Cygnal project rather than the
stock Cygwin one.
Example software shipping with Cygnal is the port of the TXR language to
Win32 and Win64. Installers available here:
https://bintray.com/kazinator/Binaries/TXR/
--
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 reply other threads:[~2017-07-10 18:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 18:01 Kaz Kylheku [this message]
2017-07-11 14:43 ` cyg Simple
-- strict thread matches above, loose matches on Subject: below --
2017-07-10 17:40 Nellis, Kenneth
2017-07-10 19:01 ` Hans-Bernhard Bröker
2017-07-11 14:20 ` Nellis, Kenneth
2017-07-11 14:37 ` 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=b133682e5719c0e2a546b4968a0c7233@mail.kylheku.com \
--to=920-082-4242@kylheku.com \
--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).