So trunk is now broken if you want to use vaapi. This appears to be
related to the GnashImage changes checked in last night. So as today I
was going to make the release branch, I now have a big problem. Other
than the vaaapi breakage, I think the Bitmap changes were good ones
inspite of this. Since vaapi is mostly only useful for developers at
this time, as most of it's dependencies aren't in distributions yet, I
think I'm gonna disable it in the release branch.
I'll leave it unchanged in trunk hoping the person that broke it fixes
it. Chances are more long-term is I need to refactor the vaapi support
to work with OpenVG/OpenGLES anyway.
What does anyone else think ? Is it worth delaying the code freeze to
fix this or not ? If I get zero responses like usual, I plan to disable
vaapi in the branch as mentioned.
- rob -
_______________________________________________
Gnash-dev mailing list
Gnash-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnash-dev
