[Bug 789379] wrong ffmpeg headers used during compilation

GStreamer (GNOME Bugzilla) bugzilla at gnome.org
Sat Jan 13 12:19:53 UTC 2018


https://bugzilla.gnome.org/show_bug.cgi?id=789379

Tim-Philipp Müller <t.i.m at zen.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|git master                  |1.13.1

--- Comment #4 from Tim-Philipp Müller <t.i.m at zen.co.uk> ---
Thanks for the patch!

commit 7a951369c7f7b3c16c4c4555e0df9f5ee693fc38 (HEAD -> master)
Author: U. Artie Eoff <ullysses.a.eoff at intel.com>
Date:   Mon Oct 23 19:35:31 2017 -0700

    libav: use LIBAV_CPPFLAGS for -I include paths

    Autotools automatically appends user CPPFLAGS after target
    CPPFLAGS.  Also, it puts all CPPFLAGS before CFLAGS in final
    generated gcc compile command.  The internal ffmpeg include
    paths need to come before any other external include paths
    to ensure we don't accidentally pickup external ffmpeg
    headers first (i.e. from user CPPFLAGS include paths).  Thus,
    move the internal LIBAV include paths to LIBAV_CPPFLAGS so
    that they come before any user defined CPPFLAGS.

    This allows ffmpeg and gst-ffmpeg to coexist on users system.

    https://bugzilla.gnome.org/show_bug.cgi?id=789379

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.


More information about the gstreamer-bugs mailing list