No, that's not my point. When you are configuring and building software like Matt was doing, conftest.exe will not be in the same directory as the libraries it is trying to detect support for so the system library folders always end up being searched first. Unless you were to copy those dll's into the directory where that configuration test is run, that is going to be the case.
As for python, it will report saying it can't find a particular module but its basically 1 line in a long stream of build output especially when building the package with makepkg and is *very* easily overlooked until you go looking for the module after the fact and find it missing. Python considers these modules as optional and is happy to continue along whereas in msys2, to reproduce the same build as the one in the repository, the same cannot be said. Now, after you have built your program and everything is all where it should be, then yes you are correct that there are no issues. The issue comes into play when the software is being configured and built, however, and in most cases is difficult to track down what exactly is going on especially when it requires being familiar with the DLL path search ordering listed on the above pages. On Sat, Mar 26, 2016 at 12:28 AM, Óscar Fuentes <[email protected]> wrote: > 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 ------------------------------------------------------------------------------ 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
