[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Comments on the Logging architecture in gnuradio

From: Tom Rondeau
Subject: Re: [Discuss-gnuradio] Comments on the Logging architecture in gnuradio
Date: Mon, 4 Mar 2013 18:37:01 -0500

On Mon, Mar 4, 2013 at 3:55 PM, M. Ranganathan <address@hidden> wrote:
> Suggestion for future improvement : I would love to be able to enable
> logging on a module by module basis in python for gnuradio. Right now, I see
> that many modules take a --verbose option but that's it. It is all or
> nothing.
> It would be great to have a unified logging framework (that works across
> python and c++) so logging can be configured in one place and shows up in a
> unified stream (file). It should be possible to set logging levels ( FINE,
> FINER, FINEST etc. ) to control the amount of logging.
> I was actually a bit surprised not to see such a thing given the maturity of
> the code base.
> (I know you are going to ask me to volunteer to do it :-) but perhaps an
> effort is already under way?)
> Regards,
> --
> M. Ranganathan

Funny you should ask. A new gr-logger was put into master/next /just/
this morning. If you build the Doxygen manually locally (after
updating your local checkout), there is a new "Related Pages" for

It's new, so it's not widely used. It's very simple to use from inside
a gr_block, but there's some setup to do elsewhere. I'm still thinking
of ways to make this as simple to use and ubiquitous throughout our
code as possible. But this is an excellent start, I feel.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]