Re: RFC: deploying libmingwex-0.dll

On 7/25/2017 7:56 AM, Keith Marshall via MinGW-dvlpr wrote:
> Guys,
> 
> The issue arose as an unintentionally introduced dependency, when I
> published GCC-6.3.0; I rebuilt the gcc-core-bin component, to correct
> an mpc-1.0.2 header vs. mpc-1.0.3 library dependency inconsistency,
> after I'd added libmingwex.dll.a to my cross-compiler tools.
> 
> Unintentional, it may have been, but entirely undesirable?  I'm not
> sure.  Now that this dynamic linking option is available, would it not
> be a worthwhile deployment choice to have *all* MinGW.org tools linked
> thus?  (After all, dynamic linking does have its advantages, in spite
> of the aversion shown by many Windows users).
> 
> What do you think?

Yes, it sounds like the correct thing to do.  The aversion comes from
mostly like of knowledge on managing DLL.  The users need to learn how
to store the DLL for the package so that the package uses the DLL for
their applications rather than some DLL on PATH.

-- 
Earnie

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot