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. On Thu, Oct 8, 2015 at 9:37 PM, Dr Rainer Woitok <rainer.woi...@gmail.com> wrote: > Greetings, > > 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. > > Sincerely, > Rainer > > PS: Please also reply to me personally, as I'm not subscribed to this > list. > > -- > Problem reports: http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
