VP9 - How to build?

[zerowalker]

Okay, i am not all that familiar with Mingw32, cygwin etc.

But have been trying for hours now to compile Libvpx, and to make an ffmpeg build that can encode vp9.

But i just can´t do it, i get errors here and there, and i can´t find any solutions, and i don´t know what to do anymore.

If someone could help out, i would be very grateful.

[easyfab]

Can this help ?

http://wiki.webmproject.org/ffmpeg/building-with-libvpx

[zerowalker]

I have followed that, exactly, but i am not able to build.
It fails on Libvorbis and Libvpx, Libvorbis says something about the configuration, so it seems to work if i remove "target....", but Libvpx fails on both, though it fails before even beginning to compile with "target...".

And as i am not familiar with this, i have no idea what to do.

[Kurtnoise]

Post your errors...this might help.

In order to have VP9 support in FFmpeg, you have to patch the library...

[zerowalker]

I think i am able to build Libvpx, not sure though, i changed a fail name, so not sure if it´s supposed to work or not.
The error i get though is:

[STRIP] libvpx.a < libvpx_g.a
/bin/sh: /mingw/bin/strip: Bad file number
make[1] *** [libvpx.a] Error 126
make: *** [.DEFAULT] Error 2

This goes away if i rename libvpx_g.a to libvpx.a though.

But then building ffmpeg doesn´t seem to go to well, i needed many dll files, and even after that, it didn´t seem to work.

What patch are you talking about?

[JEEB]

libvpx for at least msys/mingw has been broken for quite a while regarding that (stripping the binary to not have debug symbols that "bloat it up"). There is a patch (http://abechin.sakura.ne.jp/sblo_files/k-tai-douga/ffmpeg/libvpx-makefile.diff) for that by a Japanese guy who builds this stuff. There also used to be a thing needing patching in some of the assembly optimizations, but I'm not sure if that is needed any more.

Regarding ffmpeg and friends, you *might* want to detail into that. Also do note that depending on the defaults/type of your mingw(-w64) toolchain many things can get linked in a shared way, in which case you will also need to distribute the DLLs in order to have the binary run. There are settings and static-by-default toolchains available on the internet, of course, should you not prefer that.

[zerowalker]

Should i change to something else then? (not msys/mingw)

Well i would prefer to not require any dll files, and have everything linked in the build.
But as i am not a programmer, i really have no real knowledge of this, how to do it, or even prevent it.

Also do note that depending on the defaults/type of your mingw(-w64) toolchain many things can get linked in a shared way,
Not sure what you mean here, i got the normal Mingw, not the 64 bit version. Though i would like to build 64bit versions.