aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAnton Khirnov <anton@khirnov.net>2022-11-09 14:59:21 +0100
committerAnton Khirnov <anton@khirnov.net>2022-11-17 10:56:48 +0100
commit26080d1542c3695b6ebca127f180be102dd59af3 (patch)
tree79695c59e2f85c03d57873be339b9da21f0b27d6
parentb58264217b605d0e8f2ef1cf7d41396b6cb1617f (diff)
downloadffmpeg-26080d1542c3695b6ebca127f180be102dd59af3.tar.gz
doc/developer.texi: improve the introductory text
Remove confusing references to "external" vs. "internal" developers.
-rw-r--r--doc/developer.texi18
1 files changed, 12 insertions, 6 deletions
diff --git a/doc/developer.texi b/doc/developer.texi
index addee0d826..5cf3b19ee0 100644
--- a/doc/developer.texi
+++ b/doc/developer.texi
@@ -10,13 +10,19 @@
@contents
-@chapter Notes for external developers
+@chapter Introduction
-This document is mostly useful for internal FFmpeg developers.
-External developers who need to use the API in their application should
-refer to the API doxygen documentation in the public headers, and
-check the examples in @file{doc/examples} and in the source code to
-see how the public API is employed.
+This text is concerned with the development @emph{of} FFmpeg itself. Information
+on using the FFmpeg libraries in other programs can be found elsewhere, e.g. in:
+@itemize @bullet
+@item
+the installed header files
+@item
+@url{http://ffmpeg.org/doxygen/trunk/index.html, the Doxygen documentation}
+generated from the headers
+@item
+the examples under @file{doc/examples}
+@end itemize
You can use the FFmpeg libraries in your commercial program, but you
are encouraged to @emph{publish any patch you make}. In this case the