[FFmpeg-devel] [PATCH]Do not require pkg-config for libx265
u at pkh.me
Mon May 26 14:42:45 CEST 2014
On Mon, May 26, 2014 at 02:38:27PM +0200, Michael Niedermayer wrote:
> On Mon, May 26, 2014 at 12:46:58PM +0200, Carl Eugen Hoyos wrote:
> > On Monday 26 May 2014 12:22:03 pm Clément Bœsch wrote:
> > > So well, it's all about:
> > Yes;-)
> > > PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure --enable-foobar
> > >
> > > vs:
> > >
> > > ./configure --extra-cflags='-I/usr/local/include'
> > > --extra-ldflags='-L/usr/local/lib' --enable-foobar
> > >
> > > I'm not sure how "more difficult" the first one is over the second one.
> maybe its just me but
> on an average user system i would expect
> ./configure --enable-foobar
> to work
> /usr/local is not a "non standard" place to put stuff
pkg-config retrieves information about packages from special metadata
files. These files are named after the package, and has a .pc exten‐
sion. On most systems, pkg-config looks in /usr/lib/pkgconfig,
/usr/share/pkgconfig, /usr/local/lib/pkgconfig and
/usr/local/share/pkgconfig for these files. It will additionally look
in the colon-separated (on Windows, semicolon-separated) list of direc‐
tories specified by the PKG_CONFIG_PATH environment variable.
So if the lib is installed in /usr/local the PKG_CONFIG_PATH configuration will
not be necessary unless you want to prioritize one in /usr/local over one on
/usr (for example) .
...and thus it will add the cflags/ldflags necessary.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 490 bytes
Desc: not available
More information about the ffmpeg-devel