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
8b1a2686
Commit
8b1a2686
authored
Dec 30, 2011
by
Diego Biurrun
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
faq: Solutions for common problems with sample paths when running FATE.
parent
3f6aa85e
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
12 additions
and
0 deletions
+12
-0
faq.texi
doc/faq.texi
+12
-0
No files found.
doc/faq.texi
View file @
8b1a2686
...
...
@@ -359,4 +359,16 @@ to use them you have to append -D__STDC_CONSTANT_MACROS to your CXXFLAGS
You have to implement a URLProtocol, see @file
{
libavformat/file.c
}
in
Libav and @file
{
libmpdemux/demux
_
lavf.c
}
in MPlayer sources.
@section Why is @code
{
make fate
}
not running all tests?
Make sure you have the fate-suite samples and the @code
{
SAMPLES
}
Make variable
or @code
{
FATE
_
SAMPLES
}
environment variable or the @code
{
--samples
}
@command
{
configure
}
option is set to the right path.
@section Why is @code
{
make fate
}
not finding the samples?
Do you happen to have a @code
{
~
}
character in the samples path to indicate a
home directory? The value is used in ways where the shell cannot expand it,
causing FATE to not find files. Just replace @code
{
~
}
by the full path.
@bye
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