>Thanks for your update & write-up, looks promising :) I agree with your approach of trying to find the most lightweight C logger that does the job
Thanks for reviewing the report...
Regarding Qus 1)
>do you plan to mainly using the logger to write to files and an equivalent of `stderr` consistently across multiple platforms
Yes, this was my plan (plus the feature of dynamic change of log levels and dynamic log redirection).
>do you also plan to use it to replace some of the handling that's currently done within FreeType (like checking + parsing log levels + components, etc) with calls to that library? I believe it >would be especially interesting if we managed to move some of the components handling out of FT and into that external piece. Not sure however, if any of these libraries have a somehow >direct mapping of how components (modules) are used for tracing within FT currently (essentially, all components/modules can be configured with their own trace level).
No, I haven't thought in that direction as according to the requirements least coupling is favorable...
But, I think it is a nice idea to completely use the external logger if some user wants the feature of printing log messages to file (otherwise they can use the normal debugging facility provided by FreeType),
However, for that, we will require a logging library that provides a feature to create our own log levels (so that we could map 8 trace and other log levels which FreeType uses).
But as far as I have seen only zlog provides the feature of defining our own log levels...
Regarding Qus 2)
>have you looked into log4c at any point? Not saying it is what FreeType needs but something that worked reasonably well for me a while ago; might be a lot bigger than what we need or >have other downsides, just asking b/c I couldn't see it in your list.
I haven't looked into log4c till now...
I will have a look at log4c and update it's pros and cons (according to me and the requirements) in next week's progress report...
Thanks,
Priyesh