This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Building Cygwin from CVS


On Thu, Jan 26, 2006 at 10:12:07AM +0100, Corinna Vinschen wrote:
>On Jan 25 20:41, Joshua Daniel Franklin wrote:
>>On 1/20/06, Brian Dessent wrote:
>>>Joshua Daniel Franklin wrote:
>>>
>>>>gcc make binutils cocom dejagnu
>>>
>>>gcc depends on binutils, so there's no need to list it as requirement.
>>>Perl is used in the build process as well.
>>>
>>>http://cygwin.com/ml/cygwin/2005-01/msg01266.html
>>
>>Thanks Brian, I think I saved that email somewhere since it was
>>informative, but never acted on it.  :(
>>
>>I've added this info to
>>http://cygwin.com/faq/faq.programming.html#faq.programming.building-cygwin
>>and I'd like to put it in a winsup/README file but didn't want to touch
>>the top-level without some discussion.  Does that sound OK to do?
>
>Yes, we can add a winsup/README if you want to do this.  Would you mind
>to create a winsup README which basically follows the layout of the
>newlib README?  That would be cool.

My preference would be for build instructions in only one place, I guess
that would mean that they should be in the FAQ since that is the most visible
place.

So, I'd like the README to basically just have a URL for the cygwin web site.
And, this README should not be installed.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]