From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: 64-bit vs. 32-bit
Date: Fri, 25 Apr 2014 19:15:00 -0000 [thread overview]
Message-ID: <20140425191545.GA5191@ednor.casa.cgf.cx> (raw)
In-Reply-To: <535AA7C5.1080002@xs4all.nl>
On Fri, Apr 25, 2014 at 08:21:57PM +0200, Erwin Waterlander wrote:
>Op 25-4-2014 20:13 Tom Szczesny schreef:
>> result from uname -a
>> CYGWIN_NT-6.1-WOW64 Toshiba 1.7.17(0.262/5/3) 2012-10-19 14:39 i686 Cygwin
>
>uname -a on 64 bit cygwin should say something like:
>
>CYGWIN_NT-6.1 PC2 1.7.28(0.271/5/3) 2014-02-09 21:06 x86_64 Cygwin
>
>Note there is no "WOW64", and there is a "x86_64".
>
>>Sorry that I was not clear. I have an open source app (hosted on
>>github.com) that was developed for Linux. It compiles and works on
>>Windows-64 using my current version of Cygwin, but I suspect that I am
>>getting a 32-bit executable as a result.
>>
>>I wish to get a 64-bit executable, which I intend to redistribute to
>>other Windows users.
>>
>>Do I need to uninstall my 32-bit version of Cygwin from my laptop
>>before I install the 64-bit version of Cygwin?
>>
>No, you can have both 32 and 64 bit Cygwin installed.
Right. Just install the 64-bit Cygwin in a different location.
Note that if you distribute your executable you will have to pay
attention to the terms of the GPL - you'll need to provide all of the
source code for everything you distribute, including the Cygwin DLL.
cgf
--
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 19:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 18:13 Tom Szczesny
2014-04-25 18:21 ` Erwin Waterlander
2014-04-25 19:15 ` Christopher Faylor [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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=20140425191545.GA5191@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--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).