SG LOG: Difference between revisions
No edit summary |
Red Leader (talk | contribs) (Cleanup) |
||
Line 1: | Line 1: | ||
{{merge|SG_LOG()}} | {{merge|SG_LOG()}} | ||
<code>SG_LOG</code> is a wrapper macro for the [[SimGear]] <code>logstream</code> class. By default, the <code>logstream</code> class writes all output to the console. <code>SG_LOG</code> simplifies debugging for core developers who regularly [[Building FlightGear|compile from source]]. It allows you to easily associate your debug messages with a "channel" and with a "priority". This mechanism allows users to explicitly enable to certain log messages, while ignoring others. This can be helpful in order to troubleshoot certain problems. | |||
Logging settings can be modified using the <code>--log-level=[level]</code> [[command line]] option, detailed help about most available command line options can be obtained from the fgfs executable by calling it with the following arguments: <code>--help --verbose</code>. | |||
If you are interested in simply logging certain properties to a file at runtime, you can use either FlightGear's built-in logging framework, or the [[generic protocol]]. See [[Logging properties]] and [[Generic protocol]] for more details. | |||
== External links == | |||
* {{repo link|site=gito|proj=fg/simgear|path=simgear/debug/logstream.cxx}} | |||
* {{repo link|site=gito|proj=fg/simgear|path=simgear/debug/logstream.hxx}} | |||
* {{repo link|site=gito|proj=fg/simgear|path=simgear/debug/debug_types.h}} | |||
* | |||
* | |||
* | |||
[[Category:Core developer documentation]] | [[Category:Core developer documentation]] |
Revision as of 11:38, 5 March 2015
SG_LOG
is a wrapper macro for the SimGear logstream
class. By default, the logstream
class writes all output to the console. SG_LOG
simplifies debugging for core developers who regularly compile from source. It allows you to easily associate your debug messages with a "channel" and with a "priority". This mechanism allows users to explicitly enable to certain log messages, while ignoring others. This can be helpful in order to troubleshoot certain problems.
Logging settings can be modified using the --log-level=[level]
command line option, detailed help about most available command line options can be obtained from the fgfs executable by calling it with the following arguments: --help --verbose
.
If you are interested in simply logging certain properties to a file at runtime, you can use either FlightGear's built-in logging framework, or the generic protocol. See Logging properties and Generic protocol for more details.