Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
小白菜888
Ffmpeg
提交
9a00374c
F
Ffmpeg
项目概览
小白菜888
/
Ffmpeg
通知
3
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
DevOps
流水线
流水线任务
计划
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
F
Ffmpeg
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
DevOps
DevOps
流水线
流水线任务
计划
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
流水线任务
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
9a00374c
编写于
1月 06, 2013
作者:
D
Derek Buitenhuis
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
doc: Fix a few typos in the developer documentation
Signed-off-by:
N
Derek Buitenhuis
<
derek.buitenhuis@gmail.com
>
上级
bbae6859
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
7 addition
and
7 deletion
+7
-7
doc/developer.texi
doc/developer.texi
+7
-7
未找到文件。
doc/developer.texi
浏览文件 @
9a00374c
...
...
@@ -27,7 +27,7 @@ audio or video streams.
Shared libraries should be used whenever is possible in order to reduce
the effort distributors have to pour to support programs and to ensure
only the public
api
is used.
only the public
API
is used.
You can use Libav in your commercial program, but you must abide to the
license, LGPL or GPL depending on the specific features used, please refer
...
...
@@ -215,13 +215,13 @@ should also be avoided if they don't make the code easier to understand.
In order to configure Vim to follow Libav formatting conventions, paste
the following snippet into your @file
{
.vimrc
}
:
@example
"
indentation rules for libav: 4 spaces, no tabs
"
Indentation rules for Libav: 4 spaces, no tabs.
set expandtab
set shiftwidth=4
set softtabstop=4
set cindent
set cinoptions=(0
"
allow tabs in Makefiles
"
Allow tabs in Makefiles.
autocmd FileType make set noexpandtab shiftwidth=8 softtabstop=8
" Trailing whitespace and tabs are forbidden, so highlight them.
highlight ForbiddenWhitespace ctermbg=red guibg=red
...
...
@@ -265,8 +265,8 @@ For Emacs, add these roughly equivalent lines to your @file{.emacs.d/init.el}:
in the commit.
@item
The commit message should have a short first line in the form of
@samp
{
topic: short description
}
as
header, separated by a newline
from the body cons
ting in few lines explaining the reason of the patch
.
a @samp
{
topic: short description
}
as a
header, separated by a newline
from the body cons
isting of an explanation of why the change is necessary
.
Referring to the issue on the bug tracker does not exempt to report an
excerpt of the bug.
@item
...
...
@@ -315,7 +315,7 @@ For Emacs, add these roughly equivalent lines to your @file{.emacs.d/init.el}:
@item
Never write to unallocated memory, never write over the end of arrays,
always check values read from some untrusted source before using them
as array index or other risky things. Always use valgrind to doublecheck.
as array index or other risky things. Always use valgrind to double
-
check.
@item
Remember to check if you need to bump versions for the specific libav
parts (libavutil, libavcodec, libavformat) you are changing. You need
...
...
@@ -407,7 +407,7 @@ send a reminder by email. Your patch should eventually be dealt with.
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
}
,
If it has a
FourCC
, did you add it to @file
{
libavformat/riff.c
}
,
even if it is only a decoder?
@item
Did you add a rule to compile the appropriate files in the Makefile?
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录