Edward Diener <eldlistmaili...@tropicsoft.com> writes: > My usage of mingw-64 might be to only compile, or to compile/link, > without the need to run anything immediately.
You must admit that this type of usage is not common. [snip] > Furthermore with multiple toolchains your method of adding the > toolchains bin directory to the PATH is asking for problems. What > happens after I finish my compile/link cycle and test my program from > within some batch file created simply for that purpose by temporarily > putting some mingw-64's toolchain's bin directory in my PATH. I now go > to run my program and the temporary addition to my PATH is gone and my > program refuses to start. You shall use the same .bat for executing the binary, as explained on my first message on this thread. [snip] > And if you think that the correct way to actually permanently execute > my program is to do so from a batch file so that the correct > toolchain's bin directory is in the PATH you are in a programming > world which I am all too glad never to want to enter. "permanently"? No. If you create a binary package that is supposed to do actual work on a regular basis, and you have multiple MinGW installs, the correct approach is to copy the required dlls or use static linking, if appropriate. However, for development work, using a .bat for launching the binary is fine, even advisable. [snip] ------------------------------------------------------------------------------ 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
