In fact EXALT_LOG_DOMAIN is private. The others projects have to define it
if they want use the macros EXALT_ASSERT_*, else gcc will returns an error
(undefined EXALT_LOG_DOMAIN).
2009/9/2 Gustavo Sverzut Barbieri
> On Wed, Sep 2, 2009 at 5:06 AM, Atton Jonathan
> wrote:
> > This is not internal
On Wed, Sep 2, 2009 at 5:06 AM, Atton Jonathan wrote:
> This is not internal. I have one low level library which define a list of
> macro for doing assertion. (EXALT_ASSERT_*). These macros use EXALT_LOG_*.
> The daemon and the dbus library use these assertions, that's why EXALT_LOG
> is not intern
This is not internal. I have one low level library which define a list of
macro for doing assertion. (EXALT_ASSERT_*). These macros use EXALT_LOG_*.
The daemon and the dbus library use these assertions, that's why EXALT_LOG
is not internal.
2009/9/1 Gustavo Sverzut Barbieri
> On Tue, Sep 1, 2009
On Tue, Sep 1, 2009 at 7:14 PM, Atton Jonathan wrote:
> I suppose I can defines these 3 macros in the main library:
>
> #define EXALT_LOG_WARN(...) EINA_LOG_DOM_WARN(EXALT_LOG_DOMAIN, __VA_ARGS__)
> #define EXALT_LOG_CRIT(...) EINA_LOG_DOM_CRIT(EXALT_LOG_DOMAIN, __VA_ARGS__)
> #define EXALT_LOG_INF
I suppose I can defines these 3 macros in the main library:
#define EXALT_LOG_WARN(...) EINA_LOG_DOM_WARN(EXALT_LOG_DOMAIN, __VA_ARGS__)
#define EXALT_LOG_CRIT(...) EINA_LOG_DOM_CRIT(EXALT_LOG_DOMAIN, __VA_ARGS__)
#define EXALT_LOG_INFO(...) EINA_LOG_DOM_INFO(EXALT_LOG_DOMAIN, __VA_ARGS__)
2009/9
On Tue, Sep 1, 2009 at 4:33 PM, Enlightenment
SVN wrote:
> Log:
> Exalt: use eina_log
> - print_error(__FILE__,__func__, __LINE__,"Can not create the log
> file: %s\n",EXALTD_LOGFILE);
> + EINA_LOG_DOM_WARN(EXALT_LOG_DOMAIN,"Can not create the log file:
> %s\n",EXALTD_LOGFI
