On Tue, Dec 10, 2013 at 4:03 PM, Luca Barbato <[email protected]> wrote: > On 12/11/13 01:00, Diego Biurrun wrote: >> On Wed, Dec 11, 2013 at 12:42:26AM +0100, Luca Barbato wrote: >>> On 12/11/13 00:39, Diego Biurrun wrote: >>>> This enables a more POSIX-compliant printf implementation, that >>>> allows using length modifiers like 'z'. >>>> --- >>>> >>>> This works on the current (3.0) MinGW64 release. >>>> I still need to figure out what to do with current MinGW32. >>> >>> I'd deprecate its support. >> >> You want to deprecate MinGW32 completely? >> > > If mingw-w64 serves the purpose better I wouldn't spend more time on > that since there is plenty to do in other areas =) > > Most concerned parties I know moved to mingw-w64 since months if not years.
MinGW32 is not dead (yet), and MinGW32 still works with Libav currently. Why do you want to deprecate something that works and is being actively developed? Also some cross building environments I know about still support MinGW even if that means over 100 patches. Of course if MinGW32 is hindering development in some other more difficult-to-workaround places, then we can discuss about that separately from this thread. [...] Timothy _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
