Re: [boost] [log] Boost.Log formal review closing down

Subject: Re: [boost] [log] Boost.Log formal review closing down
From: vicente.botet (vicente.botet_at_[hidden])
Date: 2010-03-18 16:50:59

----- Original Message ----- 
From: "Zachary Turner" <divisortheory_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Thursday, March 18, 2010 8:12 PM
Subject: Re: [boost] [log] Boost.Log formal review closing down

> 
> On Thu, Mar 18, 2010 at 1:51 PM, vicente.botet <vicente.botet_at_[hidden]>wrote:
> 
>>
>> ----- Original Message -----
>> From: "Andrey Semashev" <andrey.semashev_at_[hidden]>
>> To: <boost_at_[hidden]>
>> Sent: Thursday, March 18, 2010 6:35 PM
>> Subject: Re: [boost] [log] Boost.Log formal review closing down
>>
>>
>> >
>> > On 03/18/2010 01:10 AM, vicente.botet wrote:
>> >>
>> >>>>> mc is not present in MinGW, GCC or MSVC Express. You would have to
>> >>>>> install Windows SDK or full MSVC to get it. The mc tool is expected
>> to
>> >>>>> be present in MSVC 10 Express. I have added the note to the docs in
>> >>>>> trunk about that.
>> >>>>
>> >>>> What this tool does, and can the library work without? Could this be
>> used conditionaly?
>> >>>
>> >>> It is the Message Compiler. It is required for the Event Log backend on
>> >>> Windows.
>> >>
>> >> Could this be used conditionaly?
>> >
>> > Not right now, I'm afraid. But I have plans of improving configurability
>> > of the library.
>>
>> Great. Let me know when the library will be able to run on platforms not
>> supporting wide chars, without dependencies to external tools (mc) and in
>> single thread.
>>
>>
> Unless I'm mistaken, you can already use it without dependency on external
> tools if you're not using the event log backend.  If you are using the event
> log backend, the the mc compiler isn't a requirement of boost.log, it's a
> requirement of windows itself so I don't see any obvious ways around it.

Hi,

As I said the library doesn't compiles if the platform doesn't support wide char characters (I use to work on my own computer with cygwin).

Maybe you are right, but before using the library I wanted to run the test of the library.
Once the own test of the library run on my platform I will start to try to use the library for my own needs. 
I can also remove the test that doesn't work on the platform I use, but I have no had the time to do this kind of work :(

Best,
Vicente

Best,
Vicente