From: Tony Kelman <tony@kelman.net>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: RE: Removing cygwin32-*, cygwin64-*
Date: Sun, 14 Feb 2016 12:32:00 -0000 [thread overview]
Message-ID: <BAY169-W12278F64F8B76F1E391DD4CA7AB0@phx.gbl> (raw)
In-Reply-To: <56C07023.40604@towo.net>
Achim Gratz writes:
> I guess that'd be fixable in cygport. But if you are just worried about
> having to enter the passphrase twice, you could use ssh-agent and then
> ssh with agent forwarding into the second installation (or into both
> from another box, as I do).
Yeah, just entering the passphrase from two terminals sounds way easier
than this. I'll send a patch for cygport if I take a look through its
source at any point.
Thomas Wolff writes:
> What about the mingw cross-compiling packages? Are they any good for
> (never tried)?
Yes! These are super useful for building applications that don't depend
on the Cygwin dll or require a posix libc. You use the Cygwin build
environment and all its useful tools, but then deploy the application by
itself. I find Cygwin-to-mingw cross-compilation to be better-behaved
and easier to automate than MSYS2 (having a self-hosted posix dependent
package manager is kind of a mistake on Windows), as long as you can
teach the application that you are building how to cross compile. It
ends up looking almost identical to cross-compilation from Linux using
mingw, but with the advantage that you can execute your tests too
without needing something like Wine.
-Tony
next prev parent reply other threads:[~2016-02-14 12:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 18:54 Yaakov Selkowitz
2016-02-09 19:48 ` Achim Gratz
2016-02-09 22:48 ` Andrew Schulman
2016-02-14 12:16 ` Thomas Wolff
2016-02-14 12:32 ` Tony Kelman [this message]
2016-02-13 6:59 ` Tony Kelman
2016-02-14 7:47 ` Achim Gratz
2016-03-17 10:18 ` Yaakov Selkowitz
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=BAY169-W12278F64F8B76F1E391DD4CA7AB0@phx.gbl \
--to=tony@kelman.net \
--cc=cygwin-apps@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).