[FFmpeg-devel] [PATCH] tests: don't include TARGET_PATH in the sample path needlessly

James Almer jamrial at gmail.com
Fri Apr 5 01:06:34 EEST 2019


On 4/3/2019 7:17 PM, Hendrik Leppkes wrote:
> The transcode() helper function will already prepend the TARGET_PATH to
> the sample path, if its a relative path. This avoids an issue on
> Windows, where the relative path check could fail.
> ---
>  tests/fate/ffmpeg.mak | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tests/fate/ffmpeg.mak b/tests/fate/ffmpeg.mak
> index af7282f9ab..71ab2f1f63 100644
> --- a/tests/fate/ffmpeg.mak
> +++ b/tests/fate/ffmpeg.mak
> @@ -95,7 +95,7 @@ fate-copy-trac2211-avi: CMD = transcode "h264 -r 14" $(TARGET_SAMPLES)/h264/bbc2
>  
>  FATE_STREAMCOPY-$(call ENCDEC, APNG, APNG) += fate-copy-apng
>  fate-copy-apng: fate-lavf-apng
> -fate-copy-apng: CMD = transcode apng "$(TARGET_PATH)/tests/data/lavf/lavf.apng" apng "-c:v copy"
> +fate-copy-apng: CMD = transcode apng tests/data/lavf/lavf.apng apng "-c:v copy"

Should be ok, thanks.

>  
>  FATE_STREAMCOPY-$(call DEMMUX, OGG, OGG) += fate-limited_input_seek fate-limited_input_seek-copyts
>  fate-limited_input_seek: $(TARGET_SAMPLES)/vorbis/moog_small.ogg
> 



More information about the ffmpeg-devel mailing list