This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: RFC: Cygwin 64 bit?
On Mon, Jun 27, 2011 at 11:08 AM, JonY <jon_y@users.sourceforge.net> wrote:
>>
>> Cygwin source code should really be more clean. ÂUsing some tools like
>> Source Insight(http://www.sourceinsight.com/) may be helpful.
>>
>> Maybe you can't Âstart Cygwin64 project untill Cygwin source code 's
>> cleanness reach some criteria.
>>
>> If Cygwin source code is extremely clean, then it would be easy to
>> make it 64bit clean, I think.
>>
>
> The hairy parts would be the LP64/LLP64 ABI difference. For now we need
> to decide which ABI to go with, the rest of the work will rest on this
> decision.
>
2 kinds of cleanness, general cleanness(easy to read, easy to analyze,
using tools like Source Insight), and 64 bit cleanness.
>>
>> I think single distro but with seperate bin/include/lib directories is good.
>>
>> In 64bit system, 64bit bin directory can precede 32bit Âbin directory in PATH.
>>
>> This may be implemented as Cygwin64.bat, in parallel with Cygwin.bat.
>>
>> 32bit Cygwin will be a self sustained system, Âin very long time, say,
>> Â5~10 years. Â32bit Cygwin known nothing about 64bit things.
>> But 64bit Cygwin can use 32bit Cygwin(the tools) to bootstrap itself
>> at its baby stage.
>>
>
> I was thinking that 64bit Cygwin will be installed in a completely
> separate directory so there is no chance in clobbering 32bit Cygwin
> DLLs, like a parallel 1.5/1.7 install.
>
> You also don't really need 32bit Cygwin around once 64bit Cygwin is working.
>
Yes, in a seperate directory, like /cygwin64/{bin,include,lib}
In Cygwin64's bootstrap stage(the coming 5~10 years), you really
need 32bit Cygwin's tools.
--
Chiheng Xu