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 Date: Wed, 26 Mar 2003 21:53:28 +0100 From: Marcel Telka To: cygwin AT cygwin DOT com Subject: Re: Determining the location of a Cygwin installation Message-ID: <20030326205328.GD3487@tortuga.etc.sk> References: <20030326204139 DOT GC3487 AT tortuga DOT etc DOT sk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i On Wed, Mar 26, 2003 at 03:44:29PM -0500, Igor Pechtchanski wrote: > On Wed, 26 Mar 2003, Marcel Telka wrote: > > > On Wed, Mar 26, 2003 AT 03:35:47PM -0500, Igor Pechtchanski wrote: > > > P.S. Maybe we could factor out the code that detects a Cygwin installation > > > from setup into a library, and distribute a small cygdetect.exe that links > > > with it? > > > > ... and cygdetect.exe will be placed in /bin :-) > > That wouldn't matter. Like cygcheck.exe and setup.exe, it'll be a MinGW Download like cygcheck.exe ? So, then simply download cygcheck.exe and run it with appropriate parameters... > application, independent of cygwin1.dll. You'd be able to download it > from the web (preferably from cygwin.com), and running it would output the > Windows path to /bin. -- +-------------------------------------------+ | Marcel Telka e-mail: marcel AT telka DOT sk | | homepage: http://telka.sk/ | | jabber: marcel AT jabber DOT sk | +-------------------------------------------+ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/