Hi Vipin - If you look at the linkage of the gnuradio-runtime library, you can tell whether log4cpp was used & if it was used then you know logging was enabled. If there is no log4cpp linkage in the gnuradio-runtime library, then I'm not sure how you determined whether logging was enabled. By default in an OOT, logging is disabled.
1) If you find log4cpp linkage, then in your OOT use the CMake settings enabling logging and log4cpp. 2) If you don't find log4cpp linkage, then redo the OOT build with logging enabled (but no log4cpp). Hopefully one of these will be obvious & will shed some light on the issue. In the meantime, I'm looking into fixing the logging issue; I didn't create it, exactly, but a commit of mine made it the default for OOTs. Cheers! - MLD On Mon, Jul 17, 2017, at 12:44 AM, Vipin Sharma wrote: > I can try re-building the OOT module. > > I don't think I know how to '....with logging same-same as GR's'. I have two > questions:> 1) How do I know how GR was built? With logging? > 2) Assuming I know the answer to 1) above, where do I change things so that > OOT compiles with with same setting for logging?
_______________________________________________ Discuss-gnuradio mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
