X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-3.2 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Message-ID: <4F95A702.5070709@etr-usa.com> Date: Mon, 23 Apr 2012 13:01:22 -0600 From: Warren Young User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: Cygwin-L Subject: Re: Why /usr/bin/*.dll must be executable? References: <4F915E65.8070608@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.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