Re: [boost] Boost log issues and workarounds

Subject: Re: [boost] Boost log issues and workarounds
From: hh h (jupiter.hce_at_[hidden])
Date: 2019-01-18 09:41:29

> If you want a severity level attribute, that should be severity_channel_logger_mt< ServerityLevel_t >

I added ServerityLevel_t to the severity_channel_logger_mt, but still
couldn't printed out the severity, otherwise, seems everything works.I
won't be too worry about the display of severity, finally I can
replace the google log by boost log.

BOOST_LOG_INLINE_GLOBAL_LOGGER_DEFAULT(my_logger,
src::severity_logger_mt<ServerityLevel_t>)

Thank you very much Andrey.

On 1/18/19, Andrey Semashev via Boost <boost_at_[hidden]> wrote:
> On 1/18/19 10:27 AM, hh h wrote:
>> Finally fixed it by changing LOG macro
>> (::boost::log::keywords::severity = (ServerityLevel_t::severity).
>>
>> The only thing missing is that in logging::add_file_log( ..." " <<
>> boost::log::trivial::severity << ....), that
>> boost::log::trivial::severity is empty, the keyword severity has
>> already been assigned in the macro, what I am missing here?
>
> See my other reply.
>
> Also, please keep some context of the conversation in your replies.
>
> _______________________________________________
> Unsubscribe & other changes:
> http://lists.boost.org/mailman/listinfo.cgi/boost
>