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: Mon, 15 Aug 2005 14:13:22 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Snapshots are now stripped again Message-ID: <20050815181322.GA14450@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <20050808032117.GA6731@trixie.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i 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 -- 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/