This is the mail archive of the
mailing list for the Cygwin project.
Re: Debug version of cygwin dll
- From: egor duda <deo at logos-m dot ru>
- To: Polley Christopher W <chris dot polley at ieee dot org>
- Cc: cygwin at cygwin dot com
- Date: Thu, 6 Dec 2001 12:40:50 +0300
- Subject: Re: Debug version of cygwin dll
- Organization: deo
- References: <718198F862F1D411B10F0002A50A4DB101A4F0CD@e90wwce3.dx.deere.com>
- Reply-to: egor duda <cygwin at cygwin dot com>
Thursday, 06 December, 2001 Polley Christopher W PolleyChristopherW@JohnDeere.com wrote:
PCW> Having done the make/make install from my source tree, do I have to repair
PCW> anything now?
just delete the source tree, unpack in again, rebuild in separate
PCW> Where can I find more information on the rationale behind not
PCW> building in the src directory?
in mailing list archives. many people, including core cygwin
developers, find it preferable to make builds in separate directory
not only for cygwin, but for any autoconf-managed package. So,
in-place configure is unmaintained therefore unsupported therefore not
recommended. believe me, building in separate tree makes a _lot_ of
things easier, once you're accustomed to it :)
PCW> Why does the README in the cygwin package say:
>>It is now possible to automatically configure and build a variety of
>>tools with one command. To build all of the tools contained herein,
>>run the ``configure'' script here, e.g.:
PCW> if this is the incorrect way to do it?
because it's not cygwin README. it's generic GNU package README. i
admit that it may be not clear.
Egor. mailto:email@example.com ICQ 5165414 FidoNet 2:5020/496.19
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html