X-Recipient: archive-cygwin AT delorie DOT com
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=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; 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; s=default; bh=LVnOk3pv
	73eG15Q4wt4XTYjKHhU=; b=nt7kWBMPdD3pPM5lkYTKvG3fsNPoQhxIR99TcmDw
	gEJcJkh4eBwu7NTwk+hkp/urYXPixwCUD0DRIS0nelj/ozZJBg5Dgev5grtCwnRa
	WwF2gWCJsKXQI3a36S7ohPx9rCdGQgAWWPqB/qPr6uBGfhaVIq6xLo2mNAJftVcZ
	lZ4=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Spam-SWARE-Status: No, score=-3.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,RDNS_NONE,SPF_PASS autolearn=ham version=3.3.1
MIME-Version: 1.0
X-Received: by 10.49.109.72 with SMTP id hq8mr18235597qeb.38.1375588451787; Sat, 03 Aug 2013 20:54:11 -0700 (PDT)
In-Reply-To: <51FDBA2B.8020102@tlinx.org>
References: <CADex0xxLK3LRfHcat8UYXDUoYxRu5OPzV0_+FXMKd7k_J4G+Vg AT mail DOT gmail DOT com>	<51F34FA0 DOT 50300 AT gmail DOT com>	<CADex0xwDTvHaOS-_xAr3pARiBQ19zAdOS8US06r+E14b65SC-w AT mail DOT gmail DOT com>	<51F35E4A DOT 4040207 AT gmail DOT com>	<51F368C4 DOT 5030309 AT etr-usa DOT com>	<51F9A3BE DOT 4020907 AT tlinx DOT org>	<51F9ABA0 DOT 3090205 AT etr-usa DOT com>	<51FCEA73 DOT 7030903 AT tlinx DOT org>	<CA+sc5mnr1C9HCdxdSX5FrGeOtmrRKhc11nUCC8Skj6zTQE+X9g AT mail DOT gmail DOT com>	<51FDBA2B DOT 8020102 AT tlinx DOT 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 AT users DOT sourceforge DOT net>
To: cygwin AT cygwin DOT 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