[libav-devel] [PATCH v3] lavc: external hardware frame pool initialization

2017-10-12 Thread wm4
This adds a new API, which allows the API user to query the required AVHWFramesContext parameters. This also reduces code duplication across the hwaccels by introducing ff_decode_get_hw_frames_ctx(), which uses the new API function. It takes care of initializing the hw_frames_ctx if needed, and doe

Re: [libav-devel] [PATCH] configure: fix libxavs check

2017-10-12 Thread Martin Storsjö
On Thu, 12 Oct 2017, Diego Biurrun wrote: On Thu, Oct 12, 2017 at 01:02:57AM -0300, James Almer wrote: libxavs may require pthreads and libm at link time, and without said ldflags available as global extralibs, the check will fail. Regression since 7cb1d9e2dbbe5bf4652be5d78cdd68e956fa3d63 ---

Re: [libav-devel] [PATCH] configure: fix libxavs check

2017-10-12 Thread Diego Biurrun
On Thu, Oct 12, 2017 at 07:41:15PM +0200, wm4 wrote: > On Thu, 12 Oct 2017 19:17:32 +0200 > Diego Biurrun wrote: > > On Thu, Oct 12, 2017 at 01:02:57AM -0300, James Almer wrote: > > > libxavs may require pthreads and libm at link time, and without > > > said ldflags available as global extralibs,

Re: [libav-devel] [PATCH] configure: fix libxavs check

2017-10-12 Thread Diego Biurrun
On Thu, Oct 12, 2017 at 02:36:59PM -0300, James Almer wrote: > On 10/12/2017 2:17 PM, Diego Biurrun wrote: > > On Thu, Oct 12, 2017 at 01:02:57AM -0300, James Almer wrote: > >> libxavs may require pthreads and libm at link time, and without > >> said ldflags available as global extralibs, the check

Re: [libav-devel] [PATCH] configure: fix libxavs check

2017-10-12 Thread wm4
On Thu, 12 Oct 2017 19:17:32 +0200 Diego Biurrun wrote: > On Thu, Oct 12, 2017 at 01:02:57AM -0300, James Almer wrote: > > libxavs may require pthreads and libm at link time, and without > > said ldflags available as global extralibs, the check will fail. > > > > Regression since 7cb1d9e2dbbe5bf

Re: [libav-devel] [PATCH] configure: fix libxavs check

2017-10-12 Thread James Almer
On 10/12/2017 2:17 PM, Diego Biurrun wrote: > On Thu, Oct 12, 2017 at 01:02:57AM -0300, James Almer wrote: >> libxavs may require pthreads and libm at link time, and without >> said ldflags available as global extralibs, the check will fail. >> >> Regression since 7cb1d9e2dbbe5bf4652be5d78cdd68e956

Re: [libav-devel] [PATCH] configure: fix libxavs check

2017-10-12 Thread Diego Biurrun
On Thu, Oct 12, 2017 at 01:02:57AM -0300, James Almer wrote: > libxavs may require pthreads and libm at link time, and without > said ldflags available as global extralibs, the check will fail. > > Regression since 7cb1d9e2dbbe5bf4652be5d78cdd68e956fa3d63 > --- > I tried replacing the require() ch

Re: [libav-devel] [PATCH 4/4] makedef: Add support for identifying the ARM64 machine type

2017-10-12 Thread Diego Biurrun
On Thu, Oct 12, 2017 at 11:29:10AM +0300, Martin Storsjö wrote: > Since this machine type is 5 chars while the existing ones only > were 3 (which the regexp assumed), the regexp has to be extended > a little. > --- > compat/windows/makedef | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-

Re: [libav-devel] [PATCH 3/4] configure: Add a comment about why we don't try to enable pic on arm on target_os=win32

2017-10-12 Thread Diego Biurrun
On Thu, Oct 12, 2017 at 11:29:09AM +0300, Martin Storsjö wrote: > --- > configure | 1 + > 1 file changed, 1 insertion(+) OK Diego ___ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel

Re: [libav-devel] [PATCH 2/4] configure: Don't add -fPIC to asflags when targeting windows

2017-10-12 Thread Diego Biurrun
On Thu, Oct 12, 2017 at 11:29:08AM +0300, Martin Storsjö wrote: > On X86 windows, asflags weren't actually ever used for anything, > since assembling used x86asflags instead, and that flags list > had -DPIC already. > > This fixes building shared libraries with clang for arm/aarch64 > windows. (Th

Re: [libav-devel] [PATCH 1/4] configure: Don't add -fPIC to cflags for target_os=win32

2017-10-12 Thread Diego Biurrun
On Thu, Oct 12, 2017 at 11:29:07AM +0300, Martin Storsjö wrote: > We skipped adding it to cflags for mingw/cygwin configurations > where the compiler either complains loudly or even errors out; > do the same for target_os=win32, for the case when building with > clang in msvc mode. > > This wasn't

Re: [libav-devel] [PATCH] configure: fix libxavs check

2017-10-12 Thread Luca Barbato
On 12/10/2017 06:02, James Almer wrote: libxavs may require pthreads and libm at link time, and without said ldflags available as global extralibs, the check will fail. Regression since 7cb1d9e2dbbe5bf4652be5d78cdd68e956fa3d63 Signed-off-by: James Almer --- I tried replacing the require() chec

[libav-devel] [PATCH 3/4] configure: Add a comment about why we don't try to enable pic on arm on target_os=win32

2017-10-12 Thread Martin Storsjö
--- configure | 1 + 1 file changed, 1 insertion(+) diff --git a/configure b/configure index 82cd321..fc3da8b 100755 --- a/configure +++ b/configure @@ -4400,6 +4400,7 @@ EOF .object_arch armv4 EOF +# MS armasm fails to assemble our PIC constructs [ $target_os != win32 ] && enabled_a

[libav-devel] [PATCH 4/4] makedef: Add support for identifying the ARM64 machine type

2017-10-12 Thread Martin Storsjö
Since this machine type is 5 chars while the existing ones only were 3 (which the regexp assumed), the regexp has to be extended a little. --- compat/windows/makedef | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/compat/windows/makedef b/compat/windows/makedef index fd7959

[libav-devel] [PATCH 2/4] configure: Don't add -fPIC to asflags when targeting windows

2017-10-12 Thread Martin Storsjö
On X86 windows, asflags weren't actually ever used for anything, since assembling used x86asflags instead, and that flags list had -DPIC already. This fixes building shared libraries with clang for arm/aarch64 windows. (This wasn't an issue when in msvc mode before, since we don't try to enable pi

[libav-devel] [PATCH 1/4] configure: Don't add -fPIC to cflags for target_os=win32

2017-10-12 Thread Martin Storsjö
We skipped adding it to cflags for mingw/cygwin configurations where the compiler either complains loudly or even errors out; do the same for target_os=win32, for the case when building with clang in msvc mode. This wasn't needed for the actual msvc before, since msvc uses msvc_common_flags to fil