Commit 565fd3cc authored by Clément Bœsch's avatar Clément Bœsch

doc/faq: add @command{} in the tool debug entry.

parent 2e798c6c
...@@ -475,9 +475,10 @@ read @uref{http://www.tux.org/lkml/#s15, "Programming Religion"}. ...@@ -475,9 +475,10 @@ read @uref{http://www.tux.org/lkml/#s15, "Programming Religion"}.
@section Why are the ffmpeg programs devoid of debugging symbols? @section Why are the ffmpeg programs devoid of debugging symbols?
The build process creates ffmpeg_g, ffplay_g, etc. which contain full debug The build process creates @command{ffmpeg_g}, @command{ffplay_g}, etc. which
information. Those binaries are stripped to create ffmpeg, ffplay, etc. If contain full debug information. Those binaries are stripped to create
you need the debug information, use the *_g versions. @command{ffmpeg}, @command{ffplay}, etc. If you need the debug information, use
the *_g versions.
@section I do not like the LGPL, can I contribute code under the GPL instead? @section I do not like the LGPL, can I contribute code under the GPL instead?
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment