Well, this is true: - zlib : no (cached) - iconv (libc) : no (cached) - iconv (separate) : no (cached) - icu : no (cached) - icu (lib64) : no (cached) - message-compiler : no (cached) - compiler-supports-ssse3 : yes (cached) - compiler-supports-avx2 : yes (cached) - gcc visibility : no (cached) - long double support : yes (cached) But how to fix? Thanks? -----Mensagem original----- De: Boost [mailto:boost-bounces@lists.boost.org] Em nome de Andrey Semashev Enviada em: quinta-feira, 4 de julho de 2013 15:32 Para: boost@lists.boost.org Assunto: Re: [boost] [log] Setup Windows event log backends On Thursday 04 July 2013 14:51:19 Renato Forti wrote:
Hi,
I am trying setup a basic: <http://www.boost.org/doc/libs/1_54_0/libs/log/doc/html/log/detailed/s ink_ba ckends.html#log.detailed.sink_backends.event_log> Windows event log, and I copy and past code from log documentation. My app link with:
What is wrong?
You may have compiled the library without event log support. This happens when the build system doesn't find message compiler in your PATH. When you build Boost.Log, it should say: - message-compiler : yes _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost