On 06.09.2020 06:57, Brian Inglis wrote:
On 2020-08-20 10:49, Brian Inglis wrote:
I would like to offer to adopt mingw64-x86_64-curl and mingw64-i686-curl from
Yaakov's list, as I have already adopted curl.
Releases updated to curl 7.72.0 are available for testing in:
https://drive.google.com/d
On 2020-08-20 10:49, Brian Inglis wrote:
> I would like to offer to adopt mingw64-x86_64-curl and mingw64-i686-curl from
> Yaakov's list, as I have already adopted curl.
> Releases updated to curl 7.72.0 are available for testing in:
>
> https://drive.google.com/drive/folders/1AV-n7lfK58v2nuw1ZmQr
Hamish McIntyre-Bhatty via Cygwin-apps writes:
> Oh, I wasn't very clear. I meant using 64-bit Cygwin to compile for
> 32-bit Cygwin. Could be wrong but I'm pretty sure it's been mentioned
> before.
I understood that, but please don't. The cross compilation toolchains
between Cygwin arches are se
On 2020-08-21 09:28, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> On 21/08/2020 15:24, ASSI wrote:
>> 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 symbol
On 21/08/2020 15:24, ASSI wrote:
> 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 cros
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
On 2020-08-20 14:20, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> 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 bein
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 package
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 targ
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
I would like to offer to adopt mingw64-x86_64-curl and mingw64-i686-curl from
Yaakov's list, as I have already adopted curl.
Releases updated to curl 7.72.0 are available for testing in:
https://drive.google.com/drive/folders/1AV-n7lfK58v2nuw1ZmQry-iqa-sxZ4nG?usp=sharing
Does it matter if I build
11 matches
Mail list logo
