From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 61164 invoked by alias); 8 Oct 2015 14:54:54 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 61156 invoked by uid 89); 8 Oct 2015 14:54:53 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.3 required=5.0 tests=AWL,BAYES_40,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-wi0-f169.google.com Received: from mail-wi0-f169.google.com (HELO mail-wi0-f169.google.com) (209.85.212.169) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Thu, 08 Oct 2015 14:54:51 +0000 Received: by wicgb1 with SMTP id gb1so29410754wic.1 for ; Thu, 08 Oct 2015 07:54:48 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.240.4 with SMTP id vw4mr8431239wjc.89.1444316088449; Thu, 08 Oct 2015 07:54:48 -0700 (PDT) Received: by 10.194.28.230 with HTTP; Thu, 8 Oct 2015 07:54:48 -0700 (PDT) In-Reply-To: References: <22038.29093.221000.863384@woitok.gmail.com> Date: Thu, 08 Oct 2015 14:54:00 -0000 Message-ID: Subject: Re: Running a program using a DLL under Cygwin From: Csaba Raduly To: cygwin list Cc: Rainer.Woitok@gmail.com Content-Type: text/plain; charset=UTF-8 X-SW-Source: 2015-10/txt/msg00091.txt.bz2 Hi, 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: https://msdn.microsoft.com/en-us/library/windows/desktop/ms682586%28v=vs.85%29.aspx 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 ( https://msdn.microsoft.com/en-us/library/windows/desktop/ms686203%28v=vs.85%29.aspx ) > > On Thu, Oct 8, 2015 at 9:37 PM, Dr Rainer Woitok > 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. If the CYGWIN environment contains winsymlinks:native (https://cygwin.com/cygwin-ug-net/using.html#pathnames-symlinks) , 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). Csaba -- 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 FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple