From: "Chris J. Breisch" <chris.ml@breisch.org>
To: cygwin@cygwin.com
Subject: Re: 64-bit vs. 32-bit
Date: Fri, 25 Apr 2014 22:29:00 -0000 [thread overview]
Message-ID: <535AE1AE.7060205@breisch.org> (raw)
In-Reply-To: <535AD731.8040809@etr-usa.com>
Warren Young wrote:
> On 4/25/2014 11:26, Tom Szczesny wrote:
>>
>> CYGWIN_NT-6.1-WOW64
>
> "WOW64" means 32-bit Windows emulated on top of 64-bit Windows.[1] This
> tells you that Cygwin is running inside that 32-bit environment.
>
[snip]
> You don't have to guess and hope, though. From 32-bit Cygwin:
>
> $ file /bin/ls
> /bin/ls: PE32 executable (console) Intel 80386 (stripped to external
> PDB), for MS Windows
>
> $ file /cygdrive/c/cygwin64/bin/ls
> /cygdrive/c/cygwin64/bin/ls: PE32+ executable (console) x86-64, for MS
> Windows
>
> file(1) saith sooth what what form of executable thou hast wrought.
>
> You might also find this piece enlightening: http://goo.gl/qv5ki7
>
>
That is enlightening. I have a rather different, and very non-standard
setup, making use of $PROCESSOR_ARCHITECTURE. This environment variable
is set in both 32-bit and 64-bit Cygwin. In the former, it's set to
"x86" and in the latter, it's set to "AMD64".
So, I have my 64-bit Cygwin root set to C:/cygwin/AMD64, and my 32-bit
Cygwin root set to C:/cygwin/x86. My package root for both is
C:\cygwin\packages, and I have /home in both environments mounted on
C:/cygwin/home.
I script all my builds, and the script I use sets the build directory
always to build_${PROCESSOR_ARCHITECTURE}. In a similar way, my output
files are named things like configure_${PROCESSOR_ARCHITECTURE}.out,
make_${PROCESSOR_ARCHITECTURE}.out, etc.
But, as you mention in your SO response, I'd never dream of sharing
/usr/local this way.
Oh, finally, I set the title of my mintty or xterm to contain
${PROCESSOR_ARCHITECTURE} as well, so I don't forget where I am.
--
Chris J. Breisch
--
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
next prev parent reply other threads:[~2014-04-25 22:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 17:26 Tom Szczesny
2014-04-25 17:38 ` Christopher Faylor
2014-04-25 17:47 ` Tim Prince
2014-04-25 21:44 ` Warren Young
2014-04-25 22:29 ` Chris J. Breisch [this message]
2014-04-25 18:13 Tom Szczesny
2014-04-25 18:21 ` Erwin Waterlander
2014-04-25 19:15 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=535AE1AE.7060205@breisch.org \
--to=chris.ml@breisch.org \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).