Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Date: Mon, 14 Jan 2002 19:51:52 -0500
From: Christopher Faylor <cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Documenting heap_chunk_in_mb
Message-ID: <20020115005152.GA19429@redhat.com>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <5.1.0.14.2.20020114155818.026e36d0@pop3.cris.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5.1.0.14.2.20020114155818.026e36d0@pop3.cris.com>
User-Agent: Mutt/1.3.23.1i

On Mon, Jan 14, 2002 at 03:58:37PM -0800, Randall R Schulz wrote:
>I did not, however, get any answers about the mechanics of the 
>documentation process, so my offer to help fill in this particular lacuna 
>went essentially unclaimed.
>
>So it goes...

The source code for the documentation is included with the source code
for cygwin itself.  Like nearly everything else in cygwin, it's checked
into cvs.  It's also available in the cygwin source tar ball.

I don't know precisely what tools are necessary to build the
documentation but it should be pretty obvious the first time you type
'make'.  You'll need to configure the directory to start the process
of building the documentation http://contrib.html has pointers to
how to do this if you are not familiar with the process.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/