Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Date: Mon, 15 Aug 2005 14:18:13 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: Snapshots are now stripped again
In-Reply-To: <20050815181322.GA14450@trixie.casa.cgf.cx>
Message-ID: <Pine.GSO.4.61.0508151415120.9560@slinky.cs.nyu.edu>
References: <20050808032117 DOT GA6731 AT trixie DOT casa DOT cgf DOT cx>  <Pine DOT GSO DOT 4 DOT 61 DOT 0508151404520 DOT 9560 AT slinky DOT cs DOT nyu DOT edu>  <20050815181322 DOT GA14450 AT trixie DOT casa DOT cgf DOT cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 15 Aug 2005, Christopher Faylor wrote:

> On Mon, Aug 15, 2005 at 02:06:47PM -0400, Igor Pechtchanski wrote:
> >On Sun, 7 Aug 2005, Christopher Faylor wrote:
> >>I'll be making the .dbg file available when I make the formal cygwin
> >>release also, either in the source tarball or as a separate package.
> >>
> >>The split of debug information into a separate file reflects a change
> >>to the way the Cygwin DLL is now generated by the makefile in
> >>winsup/cygwin.  Debug information will no longer be part of the DLL
> >>itself, but will, instead, only be included in the .dbg file.  There is
> >>a technical reason which prompted this change which I won't go into
> >>here, but I think the minor inconvenience of keeping the debug info in
> >>a separate place outweighs the benefits of keeping the debug info out
> >>of the DLL and making it available as a separate download.
> >
> >I noticed that the .dbg file is not part of the cygwin-inst-* tarballs.
> >Does this mean that it's not generated by the default make rule, or
> >that it's explicitly removed before generating the installation
> >tarball?
>
> It means that it is not meant to be installed by default.
>
> If you need it, download it separately.
>
> cgf

Thanks, I understood that.  I was asking a different question, though: if
a developer checked out the latest Cygwin from CVS and built it, would the
build produce the .dbg file (as it used to produce an unstripped DLL), or
would she have to invoke "make smth" separately to create it?
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. /DA

--
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/