X-Spam-Check-By: sourceware.org Date: Sat, 25 Mar 2006 12:40:51 -0500 From: Bob Rossi To: cygwin AT cygwin DOT com Subject: Re: Why only 1 cygwin1.dll? Message-ID: <20060325174051.GA9046@brasko.net> Mail-Followup-To: cygwin AT cygwin DOT com References: <032520061719 DOT 9189 DOT 44257B9C0003FD3F000023E522058891160A050E040D0C079D0A AT comcast DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 On Sat, Mar 25, 2006 at 12:38:53PM -0500, Lev Bishop wrote: > FAQ candidate? Either of Eric's explanations seem spot on, to me. And > this question does come up fairly regularly. In the FAQ, I think it would be a good idea to mention that this limitation makes it impossible (outside of setup.exe) to package an application based on Cygwin and guarantee that it runs on the host machine. That is, it's impossible to determine if the cygwin1.dll is already on the machine. Bob Rossi -- 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/