On Fri, May 05, 2017 at 06:32:18PM -0700, Aaron Levinson wrote:
> On 5/5/2017 4:50 AM, Michael Niedermayer wrote:
> > On Fri, May 05, 2017 at 11:36:05AM +0200, Hendrik Leppkes wrote:
> >> On Fri, May 5, 2017 at 9:57 AM, Clément Bœsch wrote:
> >>> On Fri, May 05, 2017 at 12:54:12AM
On 5/5/2017 4:50 AM, Michael Niedermayer wrote:
> On Fri, May 05, 2017 at 11:36:05AM +0200, Hendrik Leppkes wrote:
>> On Fri, May 5, 2017 at 9:57 AM, Clément Bœsch wrote:
>>> On Fri, May 05, 2017 at 12:54:12AM -0700, Aaron Levinson wrote:
>>> [...]
> Back to your issue: you
On Fri, May 05, 2017 at 02:17:40PM +0200, wm4 wrote:
> On Fri, 5 May 2017 14:12:56 +0200
> Michael Niedermayer wrote:
>
> > On Fri, May 05, 2017 at 09:42:51AM +0200, Clément Bœsch wrote:
> > > On Fri, May 05, 2017 at 12:11:27AM -0700, Aaron Levinson wrote:
> > > > On
On Fri, 5 May 2017 14:12:56 +0200
Michael Niedermayer wrote:
> On Fri, May 05, 2017 at 09:42:51AM +0200, Clément Bœsch wrote:
> > On Fri, May 05, 2017 at 12:11:27AM -0700, Aaron Levinson wrote:
> > > On 4/19/2017 10:43 AM, Aaron Levinson wrote:
> > > > On 4/14/2017
On Fri, May 05, 2017 at 09:42:51AM +0200, Clément Bœsch wrote:
> On Fri, May 05, 2017 at 12:11:27AM -0700, Aaron Levinson wrote:
> > On 4/19/2017 10:43 AM, Aaron Levinson wrote:
> > > On 4/14/2017 6:51 PM, Aaron Levinson wrote:
> > >> From e0c73c054add0137901d0bf7a7893e42e7e566c8 Mon Sep 17
On Fri, May 05, 2017 at 11:36:05AM +0200, Hendrik Leppkes wrote:
> On Fri, May 5, 2017 at 9:57 AM, Clément Bœsch wrote:
> > On Fri, May 05, 2017 at 12:54:12AM -0700, Aaron Levinson wrote:
> > [...]
> >> > Back to your issue: you should fix the .pc in the upstream project, this
> >> >
On Fri, May 5, 2017 at 9:57 AM, Clément Bœsch wrote:
> On Fri, May 05, 2017 at 12:54:12AM -0700, Aaron Levinson wrote:
> [...]
>> > Back to your issue: you should fix the .pc in the upstream project, this
>> > is the correct fix.
>>
>> The "upstream project" in this case is the Intel
On 5/5/2017 12:57 AM, Clément Bœsch wrote:
On Fri, May 05, 2017 at 12:54:12AM -0700, Aaron Levinson wrote:
[...]
Back to your issue: you should fix the .pc in the upstream project, this
is the correct fix.
The "upstream project" in this case is the Intel Media SDK. This is not an
open source
On Fri, May 05, 2017 at 12:54:12AM -0700, Aaron Levinson wrote:
[...]
> > Back to your issue: you should fix the .pc in the upstream project, this
> > is the correct fix.
>
> The "upstream project" in this case is the Intel Media SDK. This is not an
> open source project, and developers get it
On 5/5/2017 12:42 AM, Clément Bœsch wrote:
On Fri, May 05, 2017 at 12:11:27AM -0700, Aaron Levinson wrote:
On 4/19/2017 10:43 AM, Aaron Levinson wrote:
On 4/14/2017 6:51 PM, Aaron Levinson wrote:
From e0c73c054add0137901d0bf7a7893e42e7e566c8 Mon Sep 17 00:00:00 2001
From: Aaron Levinson
On Fri, 5 May 2017 09:42:51 +0200
Clément Bœsch wrote:
> On Fri, May 05, 2017 at 12:11:27AM -0700, Aaron Levinson wrote:
> > On 4/19/2017 10:43 AM, Aaron Levinson wrote:
> > > On 4/14/2017 6:51 PM, Aaron Levinson wrote:
> > >> From e0c73c054add0137901d0bf7a7893e42e7e566c8 Mon
On Fri, May 05, 2017 at 12:11:27AM -0700, Aaron Levinson wrote:
> On 4/19/2017 10:43 AM, Aaron Levinson wrote:
> > On 4/14/2017 6:51 PM, Aaron Levinson wrote:
> >> From e0c73c054add0137901d0bf7a7893e42e7e566c8 Mon Sep 17 00:00:00 2001
> >> From: Aaron Levinson
> >> Date:
2017-05-05 9:11 GMT+02:00 Aaron Levinson :
> And again. This patch is pretty straightforward, and considering that
> this approach was deemed suitable for libx264, I don't see why there
> would be any issue with it being applied to libmfx as well.
That's exactly what I
On 4/19/2017 10:43 AM, Aaron Levinson wrote:
> On 4/14/2017 6:51 PM, Aaron Levinson wrote:
>> From e0c73c054add0137901d0bf7a7893e42e7e566c8 Mon Sep 17 00:00:00 2001
>> From: Aaron Levinson
>> Date: Fri, 14 Apr 2017 18:38:37 -0700
>> Subject: [PATCH] Added require fallback
On 4/14/2017 6:51 PM, Aaron Levinson wrote:
From e0c73c054add0137901d0bf7a7893e42e7e566c8 Mon Sep 17 00:00:00 2001
From: Aaron Levinson
Date: Fri, 14 Apr 2017 18:38:37 -0700
Subject: [PATCH] Added require fallback for libmfx in the case that
pkg-config cannot find libmfx
On 15 April 2017 at 13:41, Aaron Levinson wrote:
> Doesn't require() already do that? Here is the contents of require():
>
> require(){
> log require "$@"
> name_version="$1"
> headers="$2"
> func="$3"
> shift 3
> check_lib "$headers" $func "$@" ||
On 4/15/2017 4:25 AM, Ricardo Constantino wrote:
> On 15 April 2017 at 02:51, Aaron Levinson wrote:
>
>> From e0c73c054add0137901d0bf7a7893e42e7e566c8 Mon Sep 17 00:00:00 2001
>> From: Aaron Levinson
>> Date: Fri, 14 Apr 2017 18:38:37 -0700
>>
On 15 April 2017 at 02:51, Aaron Levinson wrote:
> From e0c73c054add0137901d0bf7a7893e42e7e566c8 Mon Sep 17 00:00:00 2001
> From: Aaron Levinson
> Date: Fri, 14 Apr 2017 18:38:37 -0700
> Subject: [PATCH] Added require fallback for libmfx in the case
From e0c73c054add0137901d0bf7a7893e42e7e566c8 Mon Sep 17 00:00:00 2001
From: Aaron Levinson
Date: Fri, 14 Apr 2017 18:38:37 -0700
Subject: [PATCH] Added require fallback for libmfx in the case that
pkg-config cannot find libmfx
Purpose: Added require fallback for libmfx in
19 matches
Mail list logo