Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
19th June 2013, 23:20 | #1 | Link |
Registered User
Join Date: Jul 2011
Posts: 1,121
|
VP9 - How to build?
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. |
20th June 2013, 14:36 | #3 | Link |
Registered User
Join Date: Jul 2011
Posts: 1,121
|
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. |
21st June 2013, 15:00 | #5 | Link |
Registered User
Join Date: Jul 2011
Posts: 1,121
|
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? |
21st June 2013, 16:20 | #6 | Link |
もこたんインしたお!
Join Date: Jan 2008
Location: Finland / Japan
Posts: 512
|
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 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.
__________________
[I'm human, no debug]
|
22nd June 2013, 18:11 | #7 | Link | |
Registered User
Join Date: Jul 2011
Posts: 1,121
|
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. Quote:
|
|
|
|