Nellis, Kenneth writes:
> Thanx! I've changed my $PS1 prompts to keep straight which Cygwin I'm using
> based on $(arch).
> What'd be really cool is if separate Cygwin[-Terminal].ico icons would
> distinguish which bit-version
> I'm using. Yeah, I know, PTC. :-)
There's a bunch of different ter
-Original Message-
From: Achim Gratz
Nellis, Kenneth writes:
> Now, I want to share my Cygwin $HOME directory between the two
> environments. I already keep my binaries in $HOME/bin/$(arch) and
> $HOME/lib/$(arch), so they are covered. And, of course /usr/bin has to
> continue to point
Nellis, Kenneth writes:
> Now, I want to share my Cygwin $HOME directory between the two
> environments. I already keep my binaries in $HOME/bin/$(arch)
> and $HOME/lib/$(arch), so they are covered. And, of course
> /usr/bin has to continue to point to the separate Cygwin
> environments.
Mak
-Original Message-
From: Christopher Faylor 2-bit and 64-bit in a shared environment
On Wed, Jun 25, 2014 at 01:04:24PM +, Nellis, Kenneth wrote:
>I have happily been using 32-bit Cygwin for years, developing
>shell/perl scripts and C/C++ software. Some of the users that I support
>h
On Wed, Jun 25, 2014 at 01:04:24PM +, Nellis, Kenneth wrote:
>I have happily been using 32-bit Cygwin for years, developing
>shell/perl scripts and C/C++ software. Some of the users that
>I support have upgraded to 64-bit Cygwin, and so my 32-bit C/C++
>binaries no longer work for them. That
I have happily been using 32-bit Cygwin for years, developing
shell/perl scripts and C/C++ software. Some of the users that
I support have upgraded to 64-bit Cygwin, and so my 32-bit C/C++
binaries no longer work for them. That has forced me to adopt
64-bit Cygwin, which I've installed on the s
6 matches
Mail list logo
