Óscar Fuentes <[email protected]> writes: > OTOH I'm 100% sure that placing a dll on the same directory where the > binaries that depend on it are installed protects your application from > the presence of identically named dlls on the system. This is documented > again and again, including the page you link to. When a dll is > *searched*, the system follows the well-known order (directory of the > executable, current directory, etc) but once a dll was *found*, a new > attempt to load the dll with the same name will be subject to the rule > you quoted.
Of course this is all about the same process. Once the system runs a new process, it searches again for the required dlls, regardless of what was found on previous processes. See, I'm clarifying my own messages now :-) ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140 _______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
