On 3/4/2015 7:21 PM, Andreas Cadhalpun wrote: > Unfortunately XBMC is using these semi-private fields, so it gets broken by > this > change. Therefore I think it would be better to postpone this until after a > SOVERSION bump.
Why exactly should we care about a project that uses explicitly private fields, which have always been documented as such? The onus is on XBMC. - Derek _______________________________________________ ffmpeg-devel mailing list firstname.lastname@example.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel