On Sun, Oct 8, 2017 at 8:34 AM, Derek Buitenhuis wrote:
>
> Is there anything that precludes switching 2.X to pkg-config and leaving
> 1.X as is?
No, switching 2.x to pkg-config isn't dependent on dropping 1.x. But since
I plan to do both, I figure I might as well do them together since they're
On 10/8/2017 4:18 PM, Michael Bradshaw wrote:
> I can clean these up as part of the patch that drops OpenJPEG 1.x support,
> which I plan on making after the next release (though of course someone
> else is welcome to beat me to it; it seems there's a race for OpenJPEG
> patches!).
Is there anythi
I can clean these up as part of the patch that drops OpenJPEG 1.x support,
which I plan on making after the next release (though of course someone
else is welcome to beat me to it; it seems there's a race for OpenJPEG
patches!).
___
ffmpeg-devel mailing l
On Sun, 8 Oct 2017 13:43:45 +0200
Clément Bœsch wrote:
> On Sun, Oct 08, 2017 at 04:51:49PM +0530, Gyan Doshi wrote:
> > OpenJPEG 2.3 was released a few days ago. Changelog reports "No
> > API/ABI break compared to v2.2.0 but additional symbols for subset
> > of components decoding"
> >
> > This
On Sun, Oct 08, 2017 at 04:51:49PM +0530, Gyan Doshi wrote:
> OpenJPEG 2.3 was released a few days ago. Changelog reports "No API/ABI
> break compared to v2.2.0 but additional symbols for subset of components
> decoding"
>
> This patch is adapted from an earlier patch which added support for 2.2.
OpenJPEG 2.3 was released a few days ago. Changelog reports "No API/ABI
break compared to v2.2.0 but additional symbols for subset of components
decoding"
This patch is adapted from an earlier patch which added support for 2.2.
Applied and tested locally.
From c42f0c4290170cb49dc00f7898bee31d2
