[FFmpeg-devel] [RFC][PATCH 1/4] build: Support selecting yasm-compatible assembler
Reimar Döffinger
Reimar.Doeffinger at gmx.de
Wed Jan 18 19:54:01 CET 2012
On Mon, Jan 16, 2012 at 01:00:56AM +0100, Alexander Strasser wrote:
> Alexander Strasser wrote:
> > Makes it possible to select the name/path of the tool for compiling
> > the non-inline assembly code.
>
> I found these (rather disturbing) differences, when comparing configure
> outputs after I set yasm manually with "./configure --yasmexe=/usr/bin/yasm".
>
> --- ./res/b/config.log 2012-01-15 01:24:14.093801273 +0100
> +++ ./res/c/config.log 2012-01-15 01:24:14.097801273 +0100
> @@ -4969,6 +4975,7 @@
> qtrle_test='yes'
> qtrlegray_test='yes'
> quotes='""'
> +r='/usr/bin/yasm'
> r10k_decoder='yes'
> r210_decoder='yes'
> r3d_demuxer='yes'
> @@ -5327,8 +5334,8 @@
> v4l_indev='yes'
> v4l_indev_deps='linux_videodev_h'
> vaapi_deps='va_va_h'
> -value='yes'
> -var='seek_yuv_avi_test'
> +value='yasmexe'
> +var='yasmexe'
> vb_decoder='yes'
> vble_decoder='yes'
> vc1_crystalhd_decoder='yes'
>
>
> I have no clue what is going on there. Additionally I find that file
> particurly hard to look at.
I think those values are just artefacts from parsing the command-line,
whatever writes out this part probably doesn't try to be very
intelligent about it.
More information about the ffmpeg-devel
mailing list