On 03/07/2017 07:58 AM, cyg Simple wrote:
On 3/6/2017 9:03 PM, Daniel Santos wrote:
On 03/05/2017 05:08 AM, David Billinghurst wrote:
No.
LD_LIBRARY_PATH is used by dlopen ().
PATH is one of the locations searched by Windows when starting
applications, see https://msdn.microsoft.com/en-us/library/7d83bc18.aspx
Thank you for this clarification. So load-time dlls are resolved (in
ntdll.exe or some such) using PATH and run-time dlls loaded with
dlopen() are resolved with LD_LIBRARY_PATH? I'm obviously not intimate
with Cygwin's architecture, but I'm guessing that explicitly using
LoadLibrary is still going to use PATH.
You're obviously not intimate with Windows either. The search algorithm
in Windows is more involved than PATH. You need to study more.
My concern is with the dynamic portion of this behavior -- what is
affected by environment variables.
--
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
