Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in / Register
Toggle navigation
F
ffmpeg
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Packages
Packages
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
submodule
ffmpeg
Commits
40948819
Commit
40948819
authored
Dec 23, 2014
by
Nicolas George
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc/faq: explain pkg-config basic setup.
parent
32c836cb
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
50 additions
and
0 deletions
+50
-0
faq.texi
doc/faq.texi
+50
-0
No files found.
doc/faq.texi
View file @
40948819
...
...
@@ -90,6 +90,56 @@ To build FFmpeg, you need to install the development package. It is usually
called @file
{
libfoo-dev
}
or @file
{
libfoo-devel
}
. You can remove it after the
build is finished, but be sure to keep the main package.
@section How do I make @command
{
pkg-config
}
find my libraries?
Somewhere along with your libraries, there is a @file
{
.pc
}
file (or several)
in a @file
{
pkgconfig
}
directory. You need to set environment variables to
point @command
{
pkg-config
}
to these files.
If you need to @emph
{
add
}
directories to @command
{
pkg-config
}
's search list
(typical use case: library installed separately), add it to
@code
{$
PKG
_
CONFIG
_
PATH
}
:
@example
export PKG
_
CONFIG
_
PATH
=/
opt
/
x
264
/
lib
/
pkgconfig:
/
opt
/
opus
/
lib
/
pkgconfig
@end example
If you need to @emph
{
replace
}
@command
{
pkg
-
config
}
's search list
(
typical use case: cross
-
compiling
)
, set it in
@code
{$
PKG
_
CONFIG
_
LIBDIR
}
:
@example
export PKG
_
CONFIG
_
LIBDIR=/home/me/cross/usr/lib/pkgconfig:/home/me/cross/usr/local/lib/pkgconfig
@end example
If you need to know the library's internal dependencies (typical use: static
linking), add the @code
{
--static
}
option to @command
{
pkg-config
}
:
@example
./configure --pkg-config-flags=--static
@end example
@section How do I use @command
{
pkg-config
}
when cross-compiling?
The best way is to install @command
{
pkg-config
}
in your cross-compilation
environment. It will automatically use the cross-compilation libraries.
You can also use @command
{
pkg-config
}
from the host environment by
specifying explicitly @code
{
--pkg-config=pkg-config
}
to @command
{
configure
}
.
In that case, you must point @command
{
pkg-config
}
to the correct directories
using the @code
{
PKG
_
CONFIG
_
LIBDIR
}
, as explained in the previous entry.
As an intermediate solution, you can place in your cross-compilation
environment a script that calls the host @command
{
pkg-config
}
with
@code
{
PKG
_
CONFIG
_
LIBDIR
}
set. That script can look like that:
@example
#!/bin/sh
PKG
_
CONFIG
_
LIBDIR=/path/to/cross/lib/pkgconfig
export PKG
_
CONFIG
_
LIBDIR
exec /usr/bin/pkg-config "
$
@@"
@end example
@chapter Usage
@section ffmpeg does not work; what is wrong?
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment