On 01/09/2019 12:49 PM, Ken Moffat via blfs-support wrote:
On Wed, Jan 09, 2019 at 09:36:51AM +0000, Stuart via blfs-support wrote:
My BLFS system is configured with libvpx-1.7.0 and the test in
qtwebengine-everywhere-src-5.12.0 fails.
I found that the initial problem was because pkt.data.frame.height and
pkt.data.frame.width are not present in this version of? libvpx.
To fix this I made the following change:
qtwebengine-everywhere-src-5.12.0/config.tests/libvpx/libvpx.cpp
#include <vpx/vpx_encoder.h>
int main(int, char **)
{
??? vpx_codec_cx_pkt pkt;
??? // Members added (as ints) by
??? // https://chromium-review.googlesource.com/c/webm/libvpx/+/798222
??? // And changed to int arrays by
??? // https://chromium-review.googlesource.com/c/webm/libvpx/+/879089
??? //pkt.data.frame.width[0] = 0u;
??? //pkt.data.frame.height[0] = 0u;
??? pkt.data.frame.sz = 0u; // new test
??? return 0;
}
This fixed the test but not unexpectedly the main build fails with further
incompatibilities.
For now I have built qtwebengine-everywhere-src-5.12.0 without libvpx.
The build instructions do not make reference to libvpx but the output from
the qmake config step does.
So my question is should qtwebengine-everywhere-src-5.12.0 include libvpx
and if so which version ?
thanks
I think this is one of the libraries which the chromium code forked.
On my systems with libvpx-1.7.0 the qmake output has
Checking for libvpx... no
And it eventually uses the bundled version.
I have to agree with Ken. I haven't build version 5.12 yet, but for
5.11.1, I have
Checking for libvpx... no
libvpx ............................... no
in my log, although I had already built libvpx.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
