Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Contribute to GitLab
Sign in / Register
Toggle navigation
F
ffmpeg.wasm-core
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
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Linshizhi
ffmpeg.wasm-core
Commits
bbabeb56
Commit
bbabeb56
authored
Aug 28, 2012
by
Anton Khirnov
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add reminders to update the codec descriptor list with new codec IDs.
parent
7baa115a
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
5 additions
and
0 deletions
+5
-0
developer.texi
doc/developer.texi
+2
-0
avcodec.h
libavcodec/avcodec.h
+3
-0
No files found.
doc/developer.texi
View file @
bbabeb56
...
...
@@ -404,6 +404,8 @@ send a reminder by email. Your patch should eventually be dealt with.
Did you register it in @file
{
allcodecs.c
}
or @file
{
allformats.c
}
?
@item
Did you add the AVCodecID to @file
{
avcodec.h
}
?
When adding new codec IDs, also add an entry to the codec descriptor
list in @file
{
libavcodec/codec
_
desc.c
}
.
@item
If it has a fourcc, did you add it to @file
{
libavformat/riff.c
}
,
even if it is only a decoder?
...
...
libavcodec/avcodec.h
View file @
bbabeb56
...
...
@@ -88,6 +88,9 @@
* If you add a codec ID to this list, add it so that
* 1. no value of a existing codec ID changes (that would break ABI),
* 2. it is as close as possible to similar codecs.
*
* After adding new codec IDs, do not forget to add an entry to the codec
* descriptor list and bump libavcodec minor version.
*/
enum
AVCodecID
{
AV_CODEC_ID_NONE
,
...
...
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