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

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

[Nellis, Kenneth]

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 same machine as my 
32-bit Cygwin. I need to maintain both environments in parallel.

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. 

I didn't see what I was looking for in the FAQ or User Guide, 
so am looking for advice from the list.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

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

[Christopher Faylor]

On Wed, Jun 25, 2014 at 01:04:24PM +0000, 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 has forced me to adopt 
>64-bit Cygwin, which I've installed on the same machine as my 
>32-bit Cygwin. I need to maintain both environments in parallel.
>
>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. 
>
>I didn't see what I was looking for in the FAQ or User Guide, 
>so am looking for advice from the list.

I think you're looking for this:

https://cygwin.com/cygwin-ug-net/using.html#using-pathnames

i.e., use /etc/fstab to mount your home directory to the same
place in both environments.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

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

[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 +0000, 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 has forced me to adopt 64-bit Cygwin, which 
>I've installed on the same machine as my 32-bit Cygwin. I need to 
>maintain both environments in parallel.
>
>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.
>
>I didn't see what I was looking for in the FAQ or User Guide, so am 
>looking for advice from the list.

I think you're looking for this:

https://cygwin.com/cygwin-ug-net/using.html#using-pathnames

i.e., use /etc/fstab to mount your home directory to the same place in both environments.

cgf
-----Reply-----
I knew that! Anyway, works great. Thanx!

-Ken Nellis



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

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

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

Make a user mount table in /etc/fstab.d/<user> and populate it with the
appropriate mount points (most of those will be bind mounts).  In
addition, I like to keep the other Cygwin installation accessible via
the system /etc/fstab as /mnt/cygwin32 and /mnt/cygwin64 respectively,
if you want to be able to install directly into these from the other
Cygwin you also need to re-create the ...usr/bin and ..usr/lib mount
points there.  Anything I've had in /usr/src has been moved to
/mnt/share as well.  That actually works a bit too well, so I've
resorted to giving the shell windows different colors so I can remember
which Cygwin I'm working with.


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

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

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

[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 to the separate Cygwin environments.

Make a user mount table in /etc/fstab.d/<user> and populate it with the appropriate mount points (most of those will be bind mounts).  In addition, I like to keep the other Cygwin installation accessible via the system /etc/fstab as /mnt/cygwin32 and /mnt/cygwin64 respectively, if you want to be able to install directly into these from the other Cygwin you also need to re-create the ...usr/bin and ..usr/lib mount points there.  Anything I've had in /usr/src has been moved to /mnt/share as well.  That actually works a bit too well, so I've resorted to giving the shell windows different colors so I can remember which Cygwin I'm working with.

-----Reply-----
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. :-)
-Ken Nellis

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

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

[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 terminal icons in shells32.dll that I use for that.


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

Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple