DLL naming conventions

[Chris Faylor]

On Thu, Aug 31, 2000 at 01:26:53PM -0500, Matt Minnis wrote:
>Chris,
>
><<Snip>>
>
>>That means that the (so far hypothetical) DLL problems should be
>>solvable by keeping the DLLs in the same directory as the executables.
>
>Yes, windows searches the current directory first, then moves on to the path.

This is not strictly true.  Here's the load order from msdn.microsoft.com:

  1. The directory from which the application loaded. 

  2. The current directory. 

  3. Windows 95/98: The Windows system directory. Use the GetSystemDirectory
     function to get the path of this directory. 

     Windows NT/ 2000: The 32-bit Windows system directory. Use the GetSystemDirectory
     function to get the path of this directory. The name of this directory is SYSTEM32. 

  4.Windows NT/ 2000: The 16-bit Windows system directory. There is no function that
    obtains the path of this directory, but it is searched. The name of this directory
    is SYSTEM. 

  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. 

So, putting DLLs in the same directory as the application should solve the problem,
as I indicated.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com