This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Path to dynamic libraries
- From: "Gerrit P. Haase" <gerrit at familiehaase dot de>
- To: Pierre dot Habraken at imag dot fr
- Cc: cygwin at cygwin dot com
- Date: Tue, 1 Oct 2002 10:04:47 +0200
- Subject: Re: Path to dynamic libraries
- Organization: Esse keine toten Tiere
- References: <3D984527.FD112161@imag.fr><70618342759.20020930145934@familiehaase.de> <3D98826F.9EBE7861@imag.fr>
- Reply-to: "Gerrit P. Haase" <gerrit at familiehaase dot de>
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/