DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=jf
	xI0IsByPdZNJ4Dg4pR1M65Pr9AVdN7p+8X+JogyKaU0IeiSERpOx/wKFj6mG8/FB
	E6N9surQzj0Rl8v76VBRiFW1JptL2rqggXfhfOvA0q5QNGWbbXjcxwogsvQFpNv6
	51XyEa+b5pwsVt5OLPPbjy9XGTtgzBPAJC8kVemoo=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <51FDBA2B.8020102@tlinx.org>
References: <CADex0xxLK3LRfHcat8UYXDUoYxRu5OPzV0_+FXMKd7k_J4G+Vg@mail.gmail.com>	<51F34FA0.50300@gmail.com>	<CADex0xwDTvHaOS-_xAr3pARiBQ19zAdOS8US06r+E14b65SC-w@mail.gmail.com>	<51F35E4A.4040207@gmail.com>	<51F368C4.5030309@etr-usa.com>	<51F9A3BE.4020907@tlinx.org>	<51F9ABA0.3090205@etr-usa.com>	<51FCEA73.7030903@tlinx.org>	<CA+sc5mnr1C9HCdxdSX5FrGeOtmrRKhc11nUCC8Skj6zTQE+X9g@mail.gmail.com>	<51FDBA2B.8020102@tlinx.org>
Date: Sat, 3 Aug 2013 23:54:11 -0400
Message-ID: <CA+sc5mnedD4QA88fmNq31ECKA0zmeGnxjOFt_oNg4D-srLmSHg@mail.gmail.com>
Subject: Re: having 1 set of non-bin files w/separate {bin,lib}[32/64)? (was Re: please update the supported Cygwin package list ...)
From: Earnie Boyd <earnie@users.sourceforge.net>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8

On Sat, Aug 3, 2013 at 10:19 PM, Linda Walsh wrote:
> Earnie Boyd wrote:
>>
>> However you the user have a choice of where to put things.  Frankly, I
>> would use /cygwin and /cygwin32
>
> ----
>         And how does that get you the autoredirection I suggested with
> the links in Windows/syswow64 and windows/system32?

You can't you have to segregate the environments.  You don't want to
touch Windows system directories even to put Windows symlinks.

You have two differing systems which can be controlled from the
Desktop via iconed shortcuts that starts one or the other.  Windows is
smart enough to know when you have a 64bit executable and when you
don't.  However, you don't want to clash the Cygwin runtime DLL (this
is true of two Cygwin DLL with the same bitness as well) but you may
get away with forking a 32bit Cygwin process from a 64bit Cygwin
process as long as the two environments are autonomous.  But I
wouldn't count on it not giving issues.

-- 
Earnie
-- https://sites.google.com/site/earnieboyd

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