From: ASSI <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] mingw64-x86_64-curl, mingw64-i686-curl
Date: Fri, 21 Aug 2020 16:24:47 +0200 [thread overview]
Message-ID: <87lfi8krf4.fsf@Otto.invalid> (raw)
In-Reply-To: <DB7PR02MB399666C0AF828130ACCB5683E75A0@DB7PR02MB3996.eurprd02.prod.outlook.com> (Hamish McIntyre-Bhatty via Cygwin-apps's message of "Thu, 20 Aug 2020 21:20:43 +0100")
Hamish McIntyre-Bhatty via Cygwin-apps writes:
> How does cross compiling for 32-bit Cygwin work? I think it'd be useful
> for me too - in one instance I've found that stripping debug symbols can
> take 3 times as long to run under 32-bit Cygwin.
I don't cross-compile to Cygwin, only to MingW. I believe there are
some packages that are cross-compiled from Linux, but with any of these
cross-compilation options you can't actually run the tests, so that is
the reason for not doing it for Cygwin (for me anyway). Also there's
quite a bunch of software out there that doesn't really like to be
cross-compiled and needs major effort to do so.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
next prev parent reply other threads:[~2020-08-21 14:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 16:49 Brian Inglis
2020-08-20 18:18 ` Achim Gratz
2020-08-20 19:47 ` Brian Inglis
2020-08-20 20:20 ` Hamish McIntyre-Bhatty
2020-08-20 20:36 ` Brian Inglis
2020-08-21 14:24 ` ASSI [this message]
2020-08-21 15:28 ` Hamish McIntyre-Bhatty
2020-08-22 6:09 ` Brian Inglis
2020-08-22 6:17 ` ASSI
2020-09-06 4:57 ` Brian Inglis
2020-09-06 6:46 ` Marco Atzeri
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=87lfi8krf4.fsf@Otto.invalid \
--to=stromeko@nexgo.de \
--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).