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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	q=dns; s=default; b=bm8gamRQyk2zY1m1o/fSRVZFBFN1Nvhg5ozgpMk2cK7
	sSwEpgRzfQfDTmJWcLAu00KoQtU+wG7+6tHpXhcDmRC8t87a0gcw64hpH3iGxNCd
	e1Gxu1z+wY8DWsam9KXd5puIR60PYigw+bBHuy6eVI6qQPa4ZhNJz5Nff1d+ob4I
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	s=default; bh=+UICHkLAdRogvRegX2IexOyv3TY=; b=KR7+WInRPJqJf0Zha
	G42IqqO/wqik+gEt5gXM7h1/hb7SBLbQSKqpXRnJmgOiqyZIB+o+SVVs95rWZ+Vp
	2RlZpMjcHlsctGxwBMuz8FscdYA70Tueve9vYkB8+MrxhLUu7LQxYbw68QwYj6MW
	Kkt6WCHS+/eYTIAigKrzjakVK4=
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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-0.1 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO:	smtp103.biz.mail.ne1.yahoo.com
X-Yahoo-SMTP:	ycweUreswBCK.d0cygTP5tXwHncbOU7YVeVfIxOQoyRMI2IuIKLmUqE-
X-Rocket-Received:	from [192.168.10.27] (lmh_users-groups AT 24 DOT 218 DOT 75 DOT 18 with plain [98.138.105.25]) by smtp103.biz.mail.ne1.yahoo.com with SMTP; 16 May 2014 10:02:16 -0700 PDT
Message-ID:	<53764491.7090602@molconn.com>
Date:	Fri, 16 May 2014 13:02:09 -0400
From:	LMH <lmh_users-groups AT molconn DOT com>
User-Agent:	Mozilla/5.0 (Windows NT 5.1; rv:27.0) Gecko/20100101 Firefox/27.0 SeaMonkey/2.24
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: 32 and 64 bit cygwin on same machine?
References:	<CALJkNQbTbY57AMtfcFXkGJCk3wUBuZ6q8fqrsHAd=u5o2tQ29Q AT mail DOT gmail DOT com>
In-Reply-To:	<CALJkNQbTbY57AMtfcFXkGJCk3wUBuZ6q8fqrsHAd=u5o2tQ29Q@mail.gmail.com>
X-IsSubscribed:	yes

I have run multiple versions of cygwin on the same machine. In my case,
both versions were 32-bit, but I don't see how that would make a
difference. You need to make sure that the environment variable for the
path to cygwin.dll is correct so the 64-bit dll gets loaded when you
open a 64-bit terminal.  I did that my using a windows .bat file that
starts the cygwin shell and creates a properly configured local environment.

This is the .bat file I use,

:: This bat removes the C:\cygwin\bin PATH environment variable for the
cygwin1 install that is
:: loaded into the cmd shell environment block from the registry. The
C:\cygwin2\bin PATH environment
:: variable for the cygwin2 install is then added to the PATH for the
environment block. A mintty
:: terminal is started from within the cygwin2 installation. The mintty
process inherits the
:: modified environment block. When the bat file closes, a mintty
terminal (running bash) is left
:: and has the proper PATH environment to run from the cygwin2 installation.


@echo off

:: remove "C:\cygwin\bin" from PATH
set "PATH=;%PATH%;"
set "PATH=%PATH:;;=;%"
set "PATH=;%PATH:;C:\cygwin\bin;=;%;"
set "PATH=%PATH:;;=%"

set "PATH=C:\cygwin2\bin;%PATH%"
start "" /b C:\cygwin2\bin\mintty.exe -i /Cygwin-Terminal.ico -

I think you could use something similar, just make sure to name your
cygwin installation and local package directories differently for the
two installs.

Of course, you could just move your 32-bit cygwin off the machine,
deleted the cygwin path variable, and install the 64-bit version. It's
not hard to move the original version back later.

Hope this helps,

LMH


Dominic Herity wrote:
> I'm using Python and Cygwin to test a 32 bit Windows dll.
> Now I need to test a 64 bit build of the same dll.
> Can I install 32 bit and 64 bit Cygwin on the same machine and choose
> to run either 32 bit or 64 bit python to test the corresponding dll?
> Or do I need to keep them on separate machines?
> 
> Thanks
> Dominic
> 
> --
> 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
> 
> 

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

- Raw text -