Yep, same problem with the win build, 0.7.6 works fine. Since I don't use anything else than PNG anyway (is it OptiPNG or OptiTIFF, OptiGIF?), the 0.7.7 brings nothing of value so I'll stick with 0.7.6 for now, no prob.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Acknowledged. This is not a bug in OptiPNG, but a backwards-incompatible change in the more recent MinGW-w64 library that has affected the OptiPNG build. I will override that in the next release, so that I can make it work again.
Thank you for the report.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am experencing the same issue.
If optipng is compiled with msvc, wildargs.c may not work as expected.Link with setargv.obj instead of wildargs.obj as documented in https://docs.microsoft.com/en-us/cpp/c-language/expanding-wildcard-arguments should resolve this issue.
Last edit: taroxd 2018-02-06
Yep, same problem with the win build, 0.7.6 works fine. Since I don't use anything else than PNG anyway (is it OptiPNG or OptiTIFF, OptiGIF?), the 0.7.7 brings nothing of value so I'll stick with 0.7.6 for now, no prob.
Acknowledged. This is not a bug in OptiPNG, but a backwards-incompatible change in the more recent MinGW-w64 library that has affected the OptiPNG build. I will override that in the next release, so that I can make it work again.
Thank you for the report.