On Mon, Nov 12, 2012 at 8:01 AM, Václav Šmilauer wrote: > >> Common practice is to put the DLL in the $PREFIX/bin directory and to >> put the import libraries in $PREFIX/lib. Since it is common practice >> doing otherwise might upset your users. > What do you mean by import libraries here? DLLs which get > LoadLibraryEx'd at runtime and which are not needed for resolving DLL > dependencies?
If no program requires the DLL on startup then it doesn't really matter where you put them as long as the program loading the library is able to find it. There are rules declared by Microsoft for library paths when using LoadLibrary*() API. If you distribute your libraries for other developers to use then those developers would need to understand how to use those libraries and ensure they do not require the library on startup. In this case I would probably use $PREFIX/lib/VENDOR/VERSION as the path. -- Earnie -- https://sites.google.com/site/earnieboyd ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
