On 6/23/2015 07:32, Edward Diener wrote: >> >> Maybe your frustration does not allow you to understand what I wrote. >> Please read it again. I expect some difficulty with the concept of >> having multiple installs of the toolset, with varying versions and >> configurations, but there is no excuse for not understanding the point >> about the generated executables depending on the same (and more) dlls >> that cc1plus.exe depends on. Unless you pretend to emit your executables >> to the same bin directory where those dlls are, the cleanest solution is >> to add the bin directory to PATH. Yes, they could install cc1plus.exe on >> the same bin directory where g++.exe is. That would make you happy (at >> the cost of making others miserable) until the moment you realize that >> you need to set PATH anyways. > > Please explain to me why I would need to "set PATH anyways" to a > particular toolchains bin directory if the dlls needed by any particular > executable in a toolchain were in the same directory as the executable > itself. >
Because your resulting programs may need the target support DLLs to run anyway. Alternatively, use -static for all your programs to get around that.
0xD4EBC740.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical & virtual servers, alerts via email & sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
_______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
