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 Subject: Re: use of strip.exe for binary releases? From: Robert Collins To: "Roth, Kevin P." Cc: cygwin-apps AT cygwin DOT com In-Reply-To: <6EB31774D39507408D04392F40A10B2BC1FDCC AT FDYEXC202 DOT mgroupnet DOT com> References: <6EB31774D39507408D04392F40A10B2BC1FDCC AT FDYEXC202 DOT mgroupnet DOT com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.15 (Preview Release) Date: 07 Nov 2001 09:30:53 +1100 Message-Id: <1005085854.1442.43.camel@lifelesswks> Mime-Version: 1.0 X-OriginalArrivalTime: 06 Nov 2001 22:37:06.0012 (UTC) FILETIME=[8FF1E9C0:01C16713] On Wed, 2001-11-07 at 06:32, 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? If so, > are there any standard options to be used? (--strip-debug or > --strip-unneeded???) I've added this to setup.html. Rob