On Wed, May 17, 2017 at 5:37 AM, Dirk Laurie <email@example.com> wrote:
> Well, I don't have Windows 10, but a quick look at Google turns up
> "One quick fix is to copy the dll into the same directory as your program."
> That's the one I would try first (quick fixes always grab me).
> 2017-05-17 9:12 GMT+02:00 Russell Haley <firstname.lastname@example.org>:
>> So I'm starting to see the complications now. The 64 bit binary "just
>> works" on Window 10, but the 32 bit seems to still require mingw
>> (Error message "The program can't start because libgcc_s_dw2-1.dll is
>> missing from your computer").
Thanks, I'll look into that, but my gut feeling is the dll doesn't
help for running other libraries (I don't know much about mingw yet).
Chaining the mingw installer shouldn't be too difficult. My hesitation
is two fold:
1) Most "installers" from the *nix world I have found so far do not
use the MSI format (It looks like lr4win is the exception). I will be
testing this tonight potentially
2) That introducing mingw means that the "native" development IDE for
Windows still can't be used (I suppose Eclipse with CDT is an option).
VS Studio is a constant on many developer computers. It makes sense to
me that if Windows developers are a potential target audience, giving
them access to the sources through the "native" toolset would be a
good idea now that it's possible.