libsigrok

Commit Graph

Author	SHA1	Message	Date
Uwe Hermann	1352eeddd4	libsigrok/cli: Implement loglevel support. libsigrok can now be told at which loglevel to work, i.e., how many debug/error/warning output to generate. You can also query the current loglevel. In sigrok-cli it is now possible to set the loglevel via -l. For example: - Disable all output: sigrok-cli -l 0 - Only show errors: sigrok-cli -l 1 - Show errors, warnings, info, and debug messages: sigrok-cli -l 4	2011-05-05 13:06:13 +02:00
Uwe Hermann	b08024a836	libsigrok: Introduce sr_dbg/sr_info/sr_warn/sr_err. We should use these (internal) functions in libsigrok exclusively from now on, i.e. no more use of glib's g_debug() etc. These functions are only for libsigrok, the frontends use whatever logging mechanism is suitable there.	2011-04-14 10:11:08 +02:00

Author

SHA1

Message

Date

Uwe Hermann

1352eeddd4

libsigrok/cli: Implement loglevel support.

libsigrok can now be told at which loglevel to work, i.e., how many
debug/error/warning output to generate. You can also query the current
loglevel.

In sigrok-cli it is now possible to set the loglevel via -l. For example:

 - Disable all output: sigrok-cli -l 0
 - Only show errors: sigrok-cli -l 1
 - Show errors, warnings, info, and debug messages: sigrok-cli -l 4

2011-05-05 13:06:13 +02:00

Uwe Hermann

b08024a836

libsigrok: Introduce sr_dbg/sr_info/sr_warn/sr_err.

We should use these (internal) functions in libsigrok exclusively from
now on, i.e. no more use of glib's g_debug() etc.

These functions are only for libsigrok, the frontends use whatever
logging mechanism is suitable there.

2011-04-14 10:11:08 +02:00

2 Commits