Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Wed, 23 Jul 2003 10:11:54 +0100 From: Elfyn McBratney X-X-Sender: elfyn@ellixia Reply-To: cygwin@cygwin.com To: Carlo Florendo cc: cygwin@cygwin.com Subject: Re: documentation on building the cygwin dll In-Reply-To: <000901c350f9$202d62f0$200aa8c0@thorin> Message-ID: References: <001301c350e2$695f2560$200aa8c0@thorin> <000901c350f9$202d62f0$200aa8c0@thorin> Mail-Followup-To: cygwin@cygwin.com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 23 Jul 2003, Carlo Florendo wrote: > From: "Elfyn McBratney" > > > Perhaps from the heading it's a bit mis-leading, but what your looking for is > > this . > > Hello Elfyn, > > After reading the FAQ, I did exactly what was mentioned there, namely: > > I got the latest sources from CVS (a whopping 30MB+ source). Of course, this created a ./src directory. > > I then created a ./obj directory (in the same level as ./src) and went inside it. I also created a /install directory as mentioned > in > the FAQ. > > Here is a transcript of what I did (after logging in to cvs). > > > $ mkdir /install > $ cvs checkout winsup > $ mkdir obj > $ cd obj > $ ../src/configure --prefix=/install -v > configure.log 2>&1 > $ make And after a `make install' in the build directory you will have your DLL (assumming that the build didn't fail). Elfyn -- Elfyn McBratney, EMCB | http://www.nongnu.org/wwwauth/ http://www.emcb.co.uk | http://www.emcb.co.uk/webauth/ elfyn@emcb.co.uk | wwwauth-users AT nongnu DOT org -- 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/