[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnash-dev] Complilation errors
From: |
Rob Savoye |
Subject: |
Re: [Gnash-dev] Complilation errors |
Date: |
Sat, 07 May 2011 10:17:19 -0600 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.15) Gecko/20110307 Fedora/3.1.9-0.38.b3pre.fc13 Lightning/1.0b2 Thunderbird/3.1.9 |
On 05/07/11 06:01, Sandro Santilli wrote:
> AM_CONDITIONAL(HAVE_VAAPI, test x"${found_va_incl}" = xyes)
>
> But there's no code, anywhere, setting found_va_incl variable,
> so no wonder it doesnt' work.
The GNASH_PKG_FIND macro uses variable substitution to create that
name, which is why a grep won't find it.
> Try changing that line to:
>
> AM_CONDITIONAL(HAVE_VAAPI, test x"${have_ffmpeg_vaapi}" = xyes)
That's not correct either. Whether or not ffmpeg has vaapi support
shouldn't effect whether gnash build with vaapi support.
- rob -
- [Gnash-dev] Complilation errors, Roman B., 2011/05/07
- Re: [Gnash-dev] Complilation errors, Sandro Santilli, 2011/05/07
- Re: [Gnash-dev] Complilation errors,
Rob Savoye <=
- Re: [Gnash-dev] Complilation errors, Sandro Santilli, 2011/05/10
- Re: [Gnash-dev] Complilation errors, Roman B., 2011/05/10
- Re: [Gnash-dev] Complilation errors, Sandro Santilli, 2011/05/10
- Re: [Gnash-dev] Complilation errors, Roman B., 2011/05/10
- Re: [Gnash-dev] Complilation errors, Robinson Tryon, 2011/05/10
- Re: [Gnash-dev] Complilation errors, Sandro Santilli, 2011/05/11