Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Tue, 1 Oct 2002 10:04:47 +0200 From: "Gerrit P. Haase" Reply-To: "Gerrit P. Haase" Organization: Esse keine toten Tiere X-Priority: 3 (Normal) Message-ID: <31687055984.20021001100447@familiehaase.de> To: Pierre.Habraken@imag.fr CC: cygwin@cygwin.com Subject: Re: Path to dynamic libraries In-Reply-To: <3D98826F.9EBE7861@imag.fr> References: <3D984527.FD112161@imag.fr> <70618342759.20020930145934@familiehaase.de> <3D98826F.9EBE7861@imag.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Pierre schrieb: > Thanks to everyone who replied to my question. > The actual problem I am faced to is that I compiled (and tested) a > program (ddd) under Cygwin installed as H:\Cygwin and then distributed > the binaries to students who are supposed to install it on their own > box. > The problem is that the program does not operate as expected on the > students machines, apparently because most of them installed Cygwin as > C:\Cygwin and the program does not find some dll's. > So I am looking for a way to easily "translate" library path's from a > given "compile machine" to "target machines". > Any idea someone ? As stated before, the DLL's on which your application depends need to be in a directory that is included in the PATH setting. If invoked from a Cygwin/bash shell session then it is the Cygwin PATH, else the Windows PATH setting. I have c:\cygwin\bin included in my Windows PATH setting so I am able to invoke Cygwin applications from a CMD shell window without launching bash. Gerrit -- =^..^= -- 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/