On Thu, Nov 15, 2012 at 01:10:13AM +0100, Christophe wrote:
> > > Also cosmetic one, it seems that it gives a lot of output to stdout 
> > > like:
> > > menuparser_macros.c: Macros defined while parsing "||
> > > /home/amade/scripts/x11/wmaker-music-menu.sh"
> > >   WM_VERSION = ""0.95.3"", used 0 times
> > >   ...
> > > menuparser_macros.c: 14 macros
> > 
> > I am agree with Amadeusz, there are a lot of menu output. IMO this log 
> > info is useful for developers, but not for users. #IFDEF ?
> 
> Hello all,
> 
> All those display actually come from the fact that DEBUG was enabled when 
> compiling, and should not appear from the moment you configure with standard 
> options: they are already comprised inside #ifdefs.
> 
> Rodolfo,
> 
> If you happen to still find them when you try to make the package for debian 
> let us know, I'll try to have a look to see if there would be some wrong 
> default values.
> 
> 
> Regards,
> Christophe.

These ones doesn't seem configurable, and seeing as menuparser is in
WINGs I'm pretty sure it comes from there, probably all of them can be
removed.

% grep -R DDEBUG *
WINGs/Tests/Makefile.am:        -DDEBUG
WINGs/Extras/Makefile.am:       -DRESOURCE_PATH=\"$(datadir)/WINGs\" 
@HEADER_SEARCH_PATH@ -DDEBUG
WINGs/Examples/Makefile.am:     -DRESOURCE_PATH=\"$(datadir)/WINGs\" 
@HEADER_SEARCH_PATH@ -DDEBUG
WINGs/Makefile.am:AM_CPPFLAGS = -DLOCALEDIR=\"$(NLSDIR)\" 
-DRESOURCE_PATH=\"$(datadir)/WINGs\" -DDEBUG

Amadeusz


-- 
To unsubscribe, send mail to [email protected].

Reply via email to