Open GoogleCodeExporter opened 9 years ago
configure for vs9 shows msvs
$ ../libvpx/configure --target=x86_64-win64-vs9 --enable-static-msvcrt
--disable-install-docs --enable-experimental
Configuring selected codecs
enabling vp8_encoder
enabling vp8_decoder
enabling vp9_encoder
enabling vp9_decoder
Configuring for target 'x86_64-win64-vs9'
enabling x86_64
enabling runtime_cpu_detect
enabling mmx
enabling sse
enabling sse2
enabling sse3
enabling ssse3
enabling sse4_1
using msvs
disabling ccache
enabling postproc
enabling unit_tests
Bypassing toolchain for environment detection.
Creating makefiles for x86_64-win64-vs9 libs
Creating makefiles for x86_64-win64-vs9 examples
Creating makefiles for x86_64-win64-vs9 docs
Creating makefiles for x86_64-win64-vs9 solution
Whereas gcc shows using yasm
$ ../libvpx/configure --target=x86-win32-gcc --enable-experimental --disable-mu
ltithread --disable-unit-tests --prefix=/mingw
Configuring selected codecs
enabling vp8_encoder
enabling vp8_decoder
enabling vp9_encoder
enabling vp9_decoder
Configuring for target 'x86-win32-gcc'
enabling x86
enabling runtime_cpu_detect
enabling mmx
enabling sse
enabling sse2
enabling sse3
enabling ssse3
using yasm
enabling postproc
Creating makefiles for x86-win32-gcc libs
Creating makefiles for x86-win32-gcc examples
Creating makefiles for x86-win32-gcc docs
Does this mean the Visual C version disabled assembly?
If so, the instruction on 'yasm' are missing.
Original comment by fbarch...@google.com
on 21 Jan 2013 at 5:07
We'll look at this when we're closer to a release. Please use Visual Studio for
now.
Original comment by tnakam...@google.com
on 14 Mar 2013 at 10:30
Visual Studio build is the issue.
msys build no longer works.
I'm using linux msys cross build for now.
This is for current vp8, as well as vp9.
Possible impact on chromium
Original comment by fbarch...@chromium.org
on 15 Mar 2013 at 7:06
Once the stream its close we will look at this bug.
Original comment by albe...@google.com
on 28 Mar 2013 at 10:14
Original comment by albe...@google.com
on 11 Apr 2013 at 10:08
Original issue reported on code.google.com by
fbarch...@google.com
on 19 Jan 2013 at 9:46