This is the mail archive of the
mailing list for the Cygwin project.
Re: developing 32-bit and 64-bit in a shared environment
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 25 Jun 2014 10:12:47 -0400
- Subject: Re: developing 32-bit and 64-bit in a shared environment
- Authentication-results: sourceware.org; auth=none
- References: <0D835E9B9CD07F40A48423F80D3B5A702E7D8188 at USA7109MB022 dot na dot xerox dot net>
- Reply-to: cygwin at cygwin dot com
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
>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:
i.e., use /etc/fstab to mount your home directory to the same
place in both environments.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple