From: Warren Young <warren@etr-usa.com>
To: Cygwin-L <cygwin@cygwin.com>
Subject: Re: Why /usr/bin/*.dll must be executable?
Date: Mon, 23 Apr 2012 19:01:00 -0000 [thread overview]
Message-ID: <4F95A702.5070709@etr-usa.com> (raw)
In-Reply-To: <CAKw7uVjf6kt2O=u4EB4xDGgF5wCvqRmtO6v_bc51R7Qj2RFZLw@mail.gmail.com>
On 4/20/2012 7:07 AM, Václav Zeman wrote:
> This is a Windows thing.
Another aspect of the Windows Thing which I have not seen discussed yet
is the DLL load path: http://goo.gl/VA8yC
Since Windows looks for DLLs first in the *.exe directory, this is the
most reliable place to put them.
Options 2-5 in the list at the page linked above don't really apply
here. Cygwin purposely keeps itself nice and segregated from the rest
of the system, so installing DLLs under c:\Windows isn't an option, and
CWD is simply useless for our purpose here.
The only thing stopping us from using the final option in the article
(i.e. putting cyg*.dll somewhere else in the PATH) is that it would put
the DLLs off in the most fragile location allowed under the rules and it
wouldn't solve the OP's problem anyway. The DLLs would still appear in
file name completion lists, since that also searches the PATH.
--
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
next prev parent reply other threads:[~2012-04-23 19:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 13:03 De-Jian Zhao
2012-04-20 13:05 ` De-Jian Zhao
2012-04-20 13:08 ` Václav Zeman
2012-04-20 16:18 ` De-Jian Zhao
2012-04-20 16:28 ` Corinna Vinschen
2012-04-20 17:25 ` Nellis, Kenneth
2012-04-20 17:29 ` Larry Hall (Cygwin)
2012-04-20 17:37 ` De-Jian Zhao
2012-04-20 17:46 ` Larry Hall (Cygwin)
2012-04-20 17:40 ` Nellis, Kenneth
2012-04-20 17:32 ` De-Jian Zhao
2012-04-20 17:41 ` Larry Hall (Cygwin)
2012-04-20 17:47 ` De-Jian Zhao
2012-04-20 17:58 ` Larry Hall (Cygwin)
2012-04-20 18:21 ` De-Jian Zhao
2012-04-20 18:43 ` Larry Hall (Cygwin)
2012-04-20 22:10 ` Mike Kaganski
2012-04-22 2:29 ` Larry Hall (Cygwin)
2012-04-20 18:05 ` Larry Hall (Cygwin)
2012-04-23 19:01 ` Warren Young [this message]
2012-04-23 20:16 ` Larry Hall (Cygwin)
2012-04-23 22:13 ` Warren Young
2012-04-23 23:55 ` Richard Troy
2012-04-24 0:19 ` Warren Young
2012-04-24 16:49 ` Larry Hall (Cygwin)
2012-04-20 19:06 ` Jon TURNEY
2012-04-21 3:37 ` De-Jian Zhao
2012-04-23 19:02 ` Warren Young
2012-04-23 19:26 ` David Sastre Medina
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F95A702.5070709@etr-usa.com \
--to=warren@etr-usa.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).