Re: developing 32-bit and 64-bit in a shared environment

2014-06-26 Thread Achim Gratz
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

RE: developing 32-bit and 64-bit in a shared environment

2014-06-26 Thread Nellis, Kenneth
-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

Re: developing 32-bit and 64-bit in a shared environment

2014-06-25 Thread 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 to the separate Cygwin > environments. Mak

RE: developing 32-bit and 64-bit in a shared environment

2014-06-25 Thread Nellis, Kenneth
-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

Re: developing 32-bit and 64-bit in a shared environment

2014-06-25 Thread Christopher Faylor
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