Mc is on my path: C:\boost_1_54_0>mc Microsoft (R) Message Compiler Version 1.12.9200 Copyright (c) Microsoft Corporation. All rights reserved. usage: MC [-?aAbcdnouUv] [-m <length>] [-h <path>] [-e <extension>] [-r <path>] [-x <path>] [-w <file>] [-W <file>] [-z <basename> ] [-km | -um | -generateProjections | -cs <namespace>] [-mof] [-p <prefix>] [-P <prefix>] [<filename.man>] [<filename.mc>] -? - displays this message -a - input file is ANSI (default). -A - messages in .BIN file should be ANSI. -b - .BIN filename should have .mc filename included for un iqueness. -c - sets the Customer bit in all of the message Ids. -d - FACILTY and SEVERITY values in header file in decimal. Sets message values in header to decimal initially. -e <extension> - Specify the extension for the header file (1-3 chars) -h <path> - gives the path of where to create the C include file Default is .\ -m <length> - generate a warning if the size of any message exceeds <length> characters. -n - terminates all strings with null's in the message tabl es. -o - generate OLE2 header file (use HRESULT definition inst ead of status code definition) -r <path> - gives the path of where to create the RC include file and the binary message resource files it includes. Default is .\ -s <path> - generate binary resource per provider generate summary global resource MCGenResource.BIN -t <path> - validate against baseline resource -u - input file is Unicode. -U - messages in .BIN file should be Unicode (default). -v - gives verbose output. -W <file> - specifies path to winmeta.xml file. -w <file> - specifies path to eventman.xsd file. -x <path> - gives the path of where to create the .dbg C include file that maps message Ids to their symbolic name. This option can only be used with message text file. -z <basename> - gives the base name of the generated files. Default is basename of input file. <filename.man> - gives the name of manifest file to compile <filename.mc> - gives the name of a message file to compile Code Generation Options ----------------------- -km - generate Kernel Mode logging macros -um - generate User Mode logging macros -generateProjections - generate logging interfaces projectable to Java Sc ript -cs <namespace> - generate C# (managed) logging class based on FX3.5 Eventing class -css <namespace> - generate static C# (managed) logging class based on FX3.5 Eventing class -co - add callout macro to invoke user code at loggin. not availalbe for c#, and ignored. -mof - generate downlevel support for all function/macros generated. MOF file will be generated from the manifest. MOF file will be placed in the location specified by the "-h" switch. -p <prefix> - defines the macro name prefix applied to each generated logging macro. Default is "EventWrite" -P <prefix> - defines the text at the start of each event symbol name to remove before forming the macro nam es. Default is NULL. Note: Switches 'w' and 'W' are not required and will be removed in future . Note: At most one .mc and/or one .man file can be processed in one invoca tion. Note: Generated files have the Archive bit cleared. C:\boost_1_54_0> 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