This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Why /usr/bin/*.dll must be executable?

On 4/23/2012 3:01 PM, Warren Young wrote:
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.

While the windows and system directories aren't a great place to be putting DLLs that don't belong to the O/S in some way (and indeed Windows tries to discourage it actively in recent versions by keeping it off limits to users without sufficient privileges), why do you think Cygwin apps wouldn't see a DLL it needed if it were in one of these locations?

I'm in full agreement that the 16-bit system directory and "current"
directory aren't useful or appropriate options in the context of
locations for Cygwin DLLs.



A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?

Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]