virtualenv/FFmpeg
1
0
Fork 0
mirror of https://github.com/FFmpeg/FFmpeg.git synced 2024-12-23 12:43:46 +02:00
Code Issues Releases Activity

docs: Minor project name cleanup

Browse Source 
Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
This commit is contained in:
Michael Niedermayer 2011-12-08 20:07:32 +01:00
parent a4bf093e7b
commit fab97adb66
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/developer.texi
View File

@ -180,10 +180,10 @@ should also be avoided if they don't make the code easier to understand.
@end itemize @end itemize
@subsection Editor configuration @subsection Editor configuration
In order to configure Vim to follow Libav formatting conventions, paste In order to configure Vim to follow FFmpeg formatting conventions, paste
the following snippet into your @file{.vimrc}: the following snippet into your @file{.vimrc}:
@example @example
" indentation rules for libav: 4 spaces, no tabs " indentation rules for FFmpeg: 4 spaces, no tabs
set expandtab set expandtab
set shiftwidth=4 set shiftwidth=4
set softtabstop=4 set softtabstop=4
@ -299,7 +299,7 @@ For Emacs, add these roughly equivalent lines to your @file{.emacs.d/init.el}:
always check values read from some untrusted source before using them always check values read from some untrusted source before using them
as array index or other risky things. as array index or other risky things.
@item @item
Remember to check if you need to bump versions for the specific libav Remember to check if you need to bump versions for the specific libav*
parts (libavutil, libavcodec, libavformat) you are changing. You need parts (libavutil, libavcodec, libavformat) you are changing. You need
to change the version integer. to change the version integer.
Incrementing the first component means no backward compatibility to Incrementing the first component means no backward compatibility to

2
doc/faq.texi
View File

@ -451,7 +451,7 @@ See @url{http://www.parashift.com/c++-faq-lite/mixing-c-and-cpp.html#faq-32.3}
@section I'm using libavutil from within my C++ application but the compiler complains about 'UINT64_C' was not declared in this scope @section I'm using libavutil from within my C++ application but the compiler complains about 'UINT64_C' was not declared in this scope
Libav is a pure C project using C99 math features, in order to enable C++ FFmpeg is a pure C project using C99 math features, in order to enable C++
to use them you have to append -D__STDC_CONSTANT_MACROS to your CXXFLAGS to use them you have to append -D__STDC_CONSTANT_MACROS to your CXXFLAGS
@section I have a file in memory / a API different from *open/*read/ libc how do I use it with libavformat? @section I have a file in memory / a API different from *open/*read/ libc how do I use it with libavformat?