> This is a small question with much more impact as you might expect. > Old style is to put Runtime-DLL files into bin/ directory. This had > some advantages as long as you just have one target to support, but in > general isn't the best solution IMHO. > More modern gcc installs its runtime-DLL files for > cross-compiler-scenario into <target>/lib (<target>/lib64/32) along > the the import-library. This has the advantage that even for multiple > targets each target has its private destination for runtime-DLLs. So > they don't collide. Of course by this solution you need to add this > directory to your PATH-environment. > > I would prefer to install 32-bit and 64-bit DLL files into same > directories as their import-libraries are. This is by the way > additionally the same behavior as on *nix-setups. I just noticed that autoconf (glib, glut, gio, gettext) installs DLLs to bin/ by default, and so does CMAKE (vtk).
If you were to support multiple targets (which is not my case), you will have clashes in bin/ anyways? Or is the idea to have only arch-independent scripts in bin/, the rest in <target>/bin, and add <target>/bin to $PATH depending on target? Cheers, Vaclav ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
