Matt Breedlove <[email protected]> writes: > It would be nice if they had something like SetDllDirectory or > AddDllDirectory to override this behavior for child processes to > prevent these name collisions or we at least a better way of reporting > when they occur rather than failing with some mysterious error.
If you are loading the dlls on-demand (using LoadLibrary) you can use the full path and thus avoid the problem. As long as the base dlls (those which are loaded because the import symbol table of a delay-load dll references them) are on the same directory as the exe (python.exe in your case, I guess) it should work (TM). > In cases like python where it's configuring and compiling a set of > modules and continues on if it can't find the dependencies, you just > end up with a build without that particular support with nothing > obviously wrong until you try to make use of it or go through the > build logs manually. If python's build system does not clearly report the missing dependencies, thats python's fault. Who else should report those missing dependencies? ------------------------------------------------------------------------------ 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
