From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] mingw64-x86_64-curl, mingw64-i686-curl
Date: Thu, 20 Aug 2020 21:20:43 +0100 [thread overview]
Message-ID: <DB7PR02MB399666C0AF828130ACCB5683E75A0@DB7PR02MB3996.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <133cba39-79cb-fad9-610e-0b4500d4c0b9@SystematicSw.ab.ca>
[-- Attachment #1.1.1: Type: text/plain, Size: 837 bytes --]
On 20/08/2020 20:47, Brian Inglis wrote:
> On 2020-08-20 12:18, Achim Gratz wrote:
>> Brian Inglis writes:
>>> Does it matter if I build mingw64 packages under Cygwin 64 or 32 bit: do I have
>>> to match the package being built, or does it not matter?
>> FWIW, I build my cross-compiled packages under 64bit always regardless
>> of the target architecture. No particular reason for doing it that way,
>> but it turns out the compiles tend to be slightly faster on 64bit.
> Thanks Achim,
>
> I'll do the same in future as more address space under 64, frees up some in 32,
> and reduces packages to update there.
>
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.
Hamish
[-- Attachment #1.1.2: 0x87B761FE07F548D6.asc --]
[-- Type: application/pgp-keys, Size: 3235 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-08-20 20:20 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 [this message]
2020-08-20 20:36 ` Brian Inglis
2020-08-21 14:24 ` ASSI
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=DB7PR02MB399666C0AF828130ACCB5683E75A0@DB7PR02MB3996.eurprd02.prod.outlook.com \
--to=hamishmb@live.co.uk \
--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).