On Fri, Jul 22, 2011 at 2:34 PM, Marty Jack wrote:
>
>
> On 07/22/2011 04:01 PM, Tiago Vignatti wrote:
>> Hi all,
>>
>> I wanted to use an already existent library for logging; the first that came
>> to my mind was one with syslog interface. I like because there is a lot of
>> implementations arou
On 07/22/2011 04:01 PM, Tiago Vignatti wrote:
> Hi all,
>
> I wanted to use an already existent library for logging; the first that came
> to my mind was one with syslog interface. I like because there is a lot of
> implementations around, it's simple and kinda flexible. For instance, I can
> g
Signed-off-by: Tiago Vignatti
---
clients/simple-egl.c|4
compositor/compositor.c |4
2 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/clients/simple-egl.c b/clients/simple-egl.c
index f2a1f77..9941164 100644
--- a/clients/simple-egl.c
+++ b/clients/simple-egl.
Three level of messages are possible, which are sent to syslog: WL_INFO,
WL_WARNING and WL_ERROR; the last two are printed also to stderr due
sanity. The only interface for the compositor and clients is
void wl_log(int level, const char *f, ...);
It requires a small intervention on the system
Hi all,
I wanted to use an already existent library for logging; the first that came
to my mind was one with syslog interface. I like because there is a lot of
implementations around, it's simple and kinda flexible. For instance, I can get
the whole system log together with the Wayland one if I wa
