Hard real-time logging, something which was not supported by Orocos. This allows for tracing statements (eg debugging, diagnostics) to be used, and we also use it for reporting samples (as opposed to the non-real-time OCL reporting components).
We chose to use an existing logging package, and made modifications to support real-time behaviour, rather than roll our own. The current implementation directly supports logging to file and stdout, and can easily be made to support sockets, etc. This hierarchical category approach is based on the very popular log4j package (IIRC ruby's logger is based on the same concepts).
> On 14/12/2010, at 03:14 , Sylvain Joyeux wrote:
>
> > Just for my information ...
> >
> > Sylvain
>
> Hard real-time logging, something which was not supported by Orocos. This
> allows for tracing statements (eg debugging, diagnostics) to be used, and we
> also use it for reporting samples (as opposed to the non-real-time OCL
> reporting components).
>
> We chose to use an existing logging package, and made modifications to
> support real-time behaviour, rather than roll our own. The current
> implementation directly supports logging to file and stdout, and can easily
> be made to support sockets, etc. This hierarchical category approach is
> based on the very popular log4j package (IIRC ruby's logger is based on the
> same concepts).
>
> HTH
> S
>
> --
> Orocos-Dev mailing list
> Orocos-Dev [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
>
> Is there any documentation in order to help its implementation ? My code with 2.1 experimental log4cpp is not working any more and http://www.orocos.org/wiki/rtt/rtt-20/real-time-logging/using-real-time-... seems out of date.
>
> 2010/12/13 S Roderick <kiwi [dot] net [..] ...>
> On 14/12/2010, at 03:14 , Sylvain Joyeux wrote:
>
> > Just for my information ...
> >
> > Sylvain
>
> Hard real-time logging, something which was not supported by Orocos. This allows for tracing statements (eg debugging, diagnostics) to be used, and we also use it for reporting samples (as opposed to the non-real-time OCL reporting components).
>
> We chose to use an existing logging package, and made modifications to support real-time behaviour, rather than roll our own. The current implementation directly supports logging to file and stdout, and can easily be made to support sockets, etc. This hierarchical category approach is based on the very popular log4j package (IIRC ruby's logger is based on the same concepts).
>
> HTH
> S
>
The only documentation to date, is the wiki page you noted. I don't have a working v2 implementation, so I can't say if things have changed, but the v2 patches I've seen for log4cpp don't appear to change things. You should be able to work off of that page.
I did not top post anything, your answer to Sylvain is in... You have
already told me once, I've learned :)
mainly ocl/Category.hpp has disappeared from my include/ocl directory (I
boostraped 2.2 from zero in a new folder)
2010/12/14 Stephen Roderick <kiwi [dot] net [..] ...>
> Please don't top post ...
>
> On 14/12/2010, at 12:10 , Willy Lambert wrote:
>
> Is there any documentation in order to help its implementation ? My code
> with 2.1 experimental log4cpp is not working any more and
> http://www.orocos.org/wiki/rtt/rtt-20/real-time-logging/using-real-time-... out of date.
>
> 2010/12/13 S Roderick <kiwi [dot] net [..] ...>
>
>> On 14/12/2010, at 03:14 , Sylvain Joyeux wrote:
>>
>> > Just for my information ...
>> >
>> > Sylvain
>>
>> Hard real-time logging, something which was not supported by Orocos. This
>> allows for tracing statements (eg debugging, diagnostics) to be used, and we
>> also use it for reporting samples (as opposed to the non-real-time OCL
>> reporting components).
>>
>> We chose to use an existing logging package, and made modifications to
>> support real-time behaviour, rather than roll our own. The current
>> implementation directly supports logging to file and stdout, and can easily
>> be made to support sockets, etc. This hierarchical category approach is
>> based on the very popular log4j package (IIRC ruby's logger is based on the
>> same concepts).
>>
>> HTH
>> S
>>
>>
> The only documentation to date, is the wiki page you noted. I don't have a
> working v2 implementation, so I can't say if things have changed, but the v2
> patches I've seen for log4cpp don't appear to change things. You should be
> able to work off of that page.
>
> How does your code "not work"?
>
> S
>
On Tuesday 14 December 2010 07:31:05 Willy Lambert wrote:
> I did not top post anything, your answer to Sylvain is in... You have
> already told me once, I've learned :)
What you do here *is* top-posting. The idea is that you put your reply below
the text of the guy you reply to. More specifically, below the
question/statement you reply to.
>
> mainly ocl/Category.hpp has disappeared from my include/ocl directory (I
> boostraped 2.2 from zero in a new folder)
BUILD_LOGGING is disabled by default. That's an error, since log4cpp is always
there. I'll push an 'ON' to the toolchain-2.2 branch.
> On Tuesday 14 December 2010 07:31:05 Willy Lambert wrote:
> > I did not top post anything, your answer to Sylvain is in... You have
> > already told me once, I've learned :)
>
> What you do here *is* top-posting. The idea is that you put your reply
> below
> the text of the guy you reply to. More specifically, below the
> question/statement you reply to.
>
>
ok ok i'll write here :p
> >
> > mainly ocl/Category.hpp has disappeared from my include/ocl directory (I
> > boostraped 2.2 from zero in a new folder)
>
> BUILD_LOGGING is disabled by default. That's an error, since log4cpp is
> always
> there. I'll push an 'ON' to the toolchain-2.2 branch.
>
>
I thougth it was define somewhere in my autoproj config file (like overrides
or init). It'll test this
What is log4cpp for ?
On 14/12/2010, at 03:14 , Sylvain Joyeux wrote:
> Just for my information ...
>
> Sylvain
Hard real-time logging, something which was not supported by Orocos. This allows for tracing statements (eg debugging, diagnostics) to be used, and we also use it for reporting samples (as opposed to the non-real-time OCL reporting components).
We chose to use an existing logging package, and made modifications to support real-time behaviour, rather than roll our own. The current implementation directly supports logging to file and stdout, and can easily be made to support sockets, etc. This hierarchical category approach is based on the very popular log4j package (IIRC ruby's logger is based on the same concepts).
HTH
S
What is log4cpp for ?
Is there any documentation in order to help its implementation ? My code
with 2.1 experimental log4cpp is not working any more and
http://www.orocos.org/wiki/rtt/rtt-20/real-time-logging/using-real-time-...
out of date.
2010/12/13 S Roderick <kiwi [dot] net [..] ...>
> On 14/12/2010, at 03:14 , Sylvain Joyeux wrote:
>
> > Just for my information ...
> >
> > Sylvain
>
> Hard real-time logging, something which was not supported by Orocos. This
> allows for tracing statements (eg debugging, diagnostics) to be used, and we
> also use it for reporting samples (as opposed to the non-real-time OCL
> reporting components).
>
> We chose to use an existing logging package, and made modifications to
> support real-time behaviour, rather than roll our own. The current
> implementation directly supports logging to file and stdout, and can easily
> be made to support sockets, etc. This hierarchical category approach is
> based on the very popular log4j package (IIRC ruby's logger is based on the
> same concepts).
>
> HTH
> S
>
> --
> Orocos-Dev mailing list
> Orocos-Dev [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
>
What is log4cpp for ?
Please don't top post ...
On 14/12/2010, at 12:10 , Willy Lambert wrote:
> Is there any documentation in order to help its implementation ? My code with 2.1 experimental log4cpp is not working any more and http://www.orocos.org/wiki/rtt/rtt-20/real-time-logging/using-real-time-... seems out of date.
>
> 2010/12/13 S Roderick <kiwi [dot] net [..] ...>
> On 14/12/2010, at 03:14 , Sylvain Joyeux wrote:
>
> > Just for my information ...
> >
> > Sylvain
>
> Hard real-time logging, something which was not supported by Orocos. This allows for tracing statements (eg debugging, diagnostics) to be used, and we also use it for reporting samples (as opposed to the non-real-time OCL reporting components).
>
> We chose to use an existing logging package, and made modifications to support real-time behaviour, rather than roll our own. The current implementation directly supports logging to file and stdout, and can easily be made to support sockets, etc. This hierarchical category approach is based on the very popular log4j package (IIRC ruby's logger is based on the same concepts).
>
> HTH
> S
>
The only documentation to date, is the wiki page you noted. I don't have a working v2 implementation, so I can't say if things have changed, but the v2 patches I've seen for log4cpp don't appear to change things. You should be able to work off of that page.
How does your code "not work"?
S
What is log4cpp for ?
I did not top post anything, your answer to Sylvain is in... You have
already told me once, I've learned :)
mainly ocl/Category.hpp has disappeared from my include/ocl directory (I
boostraped 2.2 from zero in a new folder)
2010/12/14 Stephen Roderick <kiwi [dot] net [..] ...>
> Please don't top post ...
>
> On 14/12/2010, at 12:10 , Willy Lambert wrote:
>
> Is there any documentation in order to help its implementation ? My code
> with 2.1 experimental log4cpp is not working any more and
> http://www.orocos.org/wiki/rtt/rtt-20/real-time-logging/using-real-time-... out of date.
>
> 2010/12/13 S Roderick <kiwi [dot] net [..] ...>
>
>> On 14/12/2010, at 03:14 , Sylvain Joyeux wrote:
>>
>> > Just for my information ...
>> >
>> > Sylvain
>>
>> Hard real-time logging, something which was not supported by Orocos. This
>> allows for tracing statements (eg debugging, diagnostics) to be used, and we
>> also use it for reporting samples (as opposed to the non-real-time OCL
>> reporting components).
>>
>> We chose to use an existing logging package, and made modifications to
>> support real-time behaviour, rather than roll our own. The current
>> implementation directly supports logging to file and stdout, and can easily
>> be made to support sockets, etc. This hierarchical category approach is
>> based on the very popular log4j package (IIRC ruby's logger is based on the
>> same concepts).
>>
>> HTH
>> S
>>
>>
> The only documentation to date, is the wiki page you noted. I don't have a
> working v2 implementation, so I can't say if things have changed, but the v2
> patches I've seen for log4cpp don't appear to change things. You should be
> able to work off of that page.
>
> How does your code "not work"?
>
> S
>
What is log4cpp for ?
On Tuesday 14 December 2010 07:31:05 Willy Lambert wrote:
> I did not top post anything, your answer to Sylvain is in... You have
> already told me once, I've learned :)
What you do here *is* top-posting. The idea is that you put your reply below
the text of the guy you reply to. More specifically, below the
question/statement you reply to.
>
> mainly ocl/Category.hpp has disappeared from my include/ocl directory (I
> boostraped 2.2 from zero in a new folder)
BUILD_LOGGING is disabled by default. That's an error, since log4cpp is always
there. I'll push an 'ON' to the toolchain-2.2 branch.
Peter
What is log4cpp for ?
2010/12/14 Peter Soetens <peter [..] ...>
> On Tuesday 14 December 2010 07:31:05 Willy Lambert wrote:
> > I did not top post anything, your answer to Sylvain is in... You have
> > already told me once, I've learned :)
>
> What you do here *is* top-posting. The idea is that you put your reply
> below
> the text of the guy you reply to. More specifically, below the
> question/statement you reply to.
>
>
ok ok i'll write here :p
> >
> > mainly ocl/Category.hpp has disappeared from my include/ocl directory (I
> > boostraped 2.2 from zero in a new folder)
>
> BUILD_LOGGING is disabled by default. That's an error, since log4cpp is
> always
> there. I'll push an 'ON' to the toolchain-2.2 branch.
>
>
I thougth it was define somewhere in my autoproj config file (like overrides
or init). It'll test this
> Peter
>