This is the mail archive of the
mailing list for the Cygwin project.
Re: Running a program using a DLL under Cygwin
- From: Csaba Raduly <rcsaba at gmail dot com>
- To: cygwin list <cygwin at cygwin dot com>
- Cc: Rainer dot Woitok at gmail dot com
- Date: Thu, 8 Oct 2015 16:54:48 +0200
- Subject: Re: Running a program using a DLL under Cygwin
- Authentication-results: sourceware.org; auth=none
- References: <22038 dot 29093 dot 221000 dot 863384 at woitok dot gmail dot com> <CAJygYd3DLkzj=Va7uuU8-NSjUG6kog0YqBuvhDMMA=0vZwY+=Q at mail dot gmail dot com>
On Thu, Oct 8, 2015 at 3:56 PM, Yucong Sun wrote:
Please don't top-post (https://cygwin.com/acronyms/#TOFU)
> I think symlink is a cygwin thing. Windows won't find that DLL (just
> like you won't find it using windows explorer.)
> Windows only support loading DLL from project directory, or system32
> as far as I know.
There are rather more possibilities, listed here:
1. The directory from which the application loaded.
2. The current directory.
3. The system directory. Use the GetSystemDirectory function to get
the path of this directory.
4. The 16-bit system directory. There is no function that obtains the
path of this directory, but it is searched.
5. The Windows directory. Use the GetWindowsDirectory function to get
the path of this directory.
6. The directories that are listed in the PATH environment variable.
Note that this does not include the per-application path specified by
the App Paths registry key. The App Paths key is not used when
computing the DLL search path.
If SafeDllSearchMode is enabled, the current directory is demoted from
#2 to #5 (just before the PATH search).
There's also SetDllDirectory (
> On Thu, Oct 8, 2015 at 9:37 PM, Dr Rainer Woitok
> <email@example.com> wrote:
>> I'm running a program which requires a DLL sitting in my "~/bin/" dir-
>> ectory. Since "~/bin/" is contained in my "PATH" environment variable,
>> everything works as desired. Recently I moved the DLL elsewhere, re-
>> placing it with a symbolic link in "~/bin/". This caused the program to
>> fail to locate the DLL. Moving the DLL back in place caused the program
>> to work again.
>> Is this a Windows problem (since DLLs are Windows rather than Unix) or
>> Cygwin's? The link was created with the normal "ln -s" command. And,
>> if that matters, Cygwin is running on Vista here.
If the CYGWIN environment contains winsymlinks:native
Cygwin creates symlinks that Windows can understand. I don't know
whether Windows will load a DLL if a native symlink to the DLL is in
the PATH (or any other directories in the search list).
GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++
The Tao of math: The numbers you can count are not the real numbers.
Life is complex, with real and imaginary parts.
"Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds
"People disagree with me. I just ignore them." -- Linus Torvalds
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple