Removing cygwin32-*, cygwin64-*

Removing cygwin32-*, cygwin64-*

[Yaakov Selkowitz]

Is anyone using the cygwin32- and/or cygwin64-* cross-compiling 
toolchain for anything besides cross-building cygwin itself?  I would 
like to remove most of these from the distro if at all possible.

-- 
Yaakov

Re: Removing cygwin32-*, cygwin64-*

[Achim Gratz]

Yaakov Selkowitz writes:
> Is anyone using the cygwin32- and/or cygwin64-* cross-compiling
> toolchain for anything besides cross-building cygwin itself?  I would
> like to remove most of these from the distro if at all possible.

Never used them… :-)


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

Re: Removing cygwin32-*, cygwin64-*

[Andrew Schulman]

> Is anyone using the cygwin32- and/or cygwin64-* cross-compiling 
> toolchain for anything besides cross-building cygwin itself?  I would 
> like to remove most of these from the distro if at all possible.

FWIW, I've tried to cross-compile some of my packages between i386 and x86_64,
and it's never worked. The build always fails for one reason or another that I
can't solve.  So I gave up and no, I don't use them any more.

Re: Removing cygwin32-*, cygwin64-*

[Thomas Wolff]

Am 09.02.2016 um 23:48 schrieb Andrew Schulman:
>> Is anyone using the cygwin32- and/or cygwin64-* cross-compiling
>> toolchain for anything besides cross-building cygwin itself?  I would
>> like to remove most of these from the distro if at all possible.
> FWIW, I've tried to cross-compile some of my packages between i386 and x86_64,
> and it's never worked. The build always fails for one reason or another that I
> can't solve.  So I gave up and no, I don't use them any more.
For a package maintainer, it's not only easier, but also useful for 
testing, to simply install cygwin-32 and -64 in parallel.
No need for cross-building.
What about the mingw cross-compiling packages? Are they any good for 
(never tried)?
Thomas

RE: Removing cygwin32-*, cygwin64-*

[Tony Kelman]

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


 		 	   		  

RE: Removing cygwin32-*, cygwin64-*

[Tony Kelman]

> Is anyone using the cygwin32- and/or cygwin64-* cross-compiling
> toolchain for anything besides cross-building cygwin itself? I would
> like to remove most of these from the distro if at all possible.

Would this impact the ability to upload package builds via cygport --32 ?
I just tried

$ cygport --32 p7zip-15.09-2.cygport upload
/usr/share/cygport/lib/compilers.cygpart: line 287: i686-pc-cygwin-gcc:
command not found

from within 64 bit cygwin on my new system that doesn't have the cygwin32
cross compilers installed yet. This can be convenient to upload both
(cross-building cygwin packages hasn't worked for me either the few times
I've tried, but uploading has) from within the same authenticated ssh
session in a 64 bit terminal rather than having to also unlock my key in
the 32 bit terminal. I use a 32 bit terminal for building, but have the
build trees all under my 64-bit home (/cygdrive/c/cygwin64/home/Tony/foo).

-Tony

 		 	   		  

Re: Removing cygwin32-*, cygwin64-*

[Achim Gratz]

Tony Kelman writes:
> Would this impact the ability to upload package builds via cygport --32 ?
> I just tried
>
> $ cygport --32 p7zip-15.09-2.cygport upload
> /usr/share/cygport/lib/compilers.cygpart: line 287: i686-pc-cygwin-gcc:
> command not found
>
> from within 64 bit cygwin on my new system that doesn't have the cygwin32
> cross compilers installed yet. This can be convenient to upload both
> (cross-building cygwin packages hasn't worked for me either the few times
> I've tried, but uploading has) from within the same authenticated ssh
> session in a 64 bit terminal rather than having to also unlock my key in
> the 32 bit terminal. I use a 32 bit terminal for building, but have the
> build trees all under my 64-bit home (/cygdrive/c/cygwin64/home/Tony/foo).

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).


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada

Re: Removing cygwin32-*, cygwin64-*

[Yaakov Selkowitz]

On 2016-02-09 12:53, Yaakov Selkowitz wrote:
> Is anyone using the cygwin32- and/or cygwin64-* cross-compiling
> toolchain for anything besides cross-building cygwin itself?  I would
> like to remove most of these from the distro if at all possible.

The following packages remain in the distribution to allow 
cross-compiling Cygwin itself:

cygwin{32,64}
cygwin{32,64}-binutils
cygwin{32,64}-default-manifest
cygwin{32,64}-gcc
cygwin{32,64}-gettext
cygwin{32,64}-libbfd
cygwin{32,64}-libiconv
cygwin{32,64}-w32api-headers
cygwin{32,64}-w32api-runtime
cygwin{32,64}-zlib

Everything else has been removed.

-- 
Yaakov