X-Spam-Check-By:	sourceware.org
Date:	Thu, 26 Jan 2006 13:44:23 -0500
From:	Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Building Cygwin from CVS
Message-ID:	<20060126184423.GA304@trixie.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
References:	<43CE88C6 DOT 3070009 AT hones DOT org DOT uk> <cb51e2e0601192053lb0a0ba7i4284a2cd57e6c9e0 AT mail DOT gmail DOT com> <43D12B2C DOT 23DD92C8 AT dessent DOT net> <cb51e2e0601252041tf586afdl9cc2e32fe669e163 AT mail DOT gmail DOT com> <20060126091207 DOT GS8318 AT calimero DOT vinschen DOT de>
Mime-Version:	1.0
In-Reply-To:	<20060126091207.GS8318@calimero.vinschen.de>
User-Agent:	Mutt/1.5.11
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

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/

- Raw text -