Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Tue, 6 Nov 2001 14:35:30 -0500 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: use of strip.exe for binary releases? Message-ID: <20011106143530.A13622@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <6EB31774D39507408D04392F40A10B2BC1FDCC AT FDYEXC202 DOT mgroupnet DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6EB31774D39507408D04392F40A10B2BC1FDCC@FDYEXC202.mgroupnet.com> User-Agent: Mutt/1.3.21i On Tue, Nov 06, 2001 at 02:32:45PM -0500, Roth, Kevin P. wrote: >For my cURL binary release, should the executable (curl.exe) and/or the >library (cygcurl2.dll) be run through strip.exe before release? Yes. >If so, are there any standard options to be used? (--strip-debug or >--strip-unneeded???) Just 'strip'. No options. cgf