[FFmpeg-trac] #3218(avcodec:closed): ffmpeg does not compile with the latest git of x264

[FFmpeg]

#3218: ffmpeg does not compile with the latest git of x264
------------------------------------+-----------------------------------
             Reporter:  mmstick     |                    Owner:
                 Type:  defect      |                   Status:  closed
             Priority:  normal      |                Component:  avcodec
              Version:  git-master  |               Resolution:  invalid
             Keywords:              |               Blocked By:
             Blocking:              |  Reproduced by developer:  0
Analyzed by developer:  0           |
------------------------------------+-----------------------------------

Comment (by ubitux):

 Replying to [comment:29 cehoyos]:
 > Replying to [comment:28 ubitux]:
 > > Replying to [comment:27 cehoyos]:
 > > > Replying to [comment:26 ubitux]:
 > > > > Note for developers: we should probably depend on pkg-config for
 the x264 probing so the linker flags are automatically added.
 > > >
 > > > Would that still allow to link libx264 on a system without pkg-
 config?
 > >
 > > Can you name a relevant one?
 >
 > (OS X?)

 Really?

 > What I meant was: If I build a libx264 library and move it (and the
 header) to a place of my choice, will I still be able to build FFmpeg
 using that libx264? If not, this sounds like a very bad idea.

 I would say yes, probably with {{{--enable-libx264 --extra-
 cflags=-I/weirdplace/include --extra-ldflags="-L/weirdplace/include
 -lx264"}}}, and "only" {{{--extra-ldflags=-lx264}}} if it's in a standard
 place. Though, I'm not sure how {{{check_pkg_config()}}} behaves when
 {{{pkg-config}}} is not available though. Maybe it aborts somewhere. If
 so, we could probably be more tolerant on that regard (by assuming the
 library is present).

 By the way, x264 has a .pc since v40 (and we require >= 118).

--
Ticket URL: <https://trac.ffmpeg.org/ticket/3218#comment:31>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker