Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Reply-To: Cygwin List Message-Id: <6.2.1.2.0.20050825143414.06dfe830@pop.prospeed.net> Date: Thu, 25 Aug 2005 14:43:27 -0400 To: William Deegan , cygwin AT cygwin DOT com From: Larry Hall Subject: Re: Which snapshot file should I use? In-Reply-To: <8540148a05082511237cf21bc9@mail.gmail.com> References: <8540148a05082511237cf21bc9 AT mail DOT gmail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 02:23 PM 8/25/2005, you wrote: >Greetings, Reformatting: >I'm wondering under what circumstances do I use each of the above? >I see the following files on the snapshot page: >winsup-src-*.tar.bz2 sources in the winsup directory Use this when you just want to have the Cygwin source or some other specialized use. >cygwin1-*.dll.bz2 stripped and compressed cygwin1.dll Use this when you just want to run with a new DLL. >cygwin1-*.dbg.bz2 debugging information for cygwin1.dll (rename to >/bin/cygwin1.dbg for use with gdb) Should be obvious. ;-) >cygwin-inst-*.tar.bz2 directory from "make install" (dll, exes, >libs, headers, etc) Use this if you plan to build stuff against the new DLL (but not the DLL itself.) Used in conjunction with cygwin1-*.dll.bz2. >cygwin-src-*.tar.bz2 all sources needed to build cygwin1.dll >(winsup, newlib, etc) Should be obvious. ;-) -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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/