office-gobmx/writerfilter/debug_setup.mk

define writerfilter_debug_flags
$(if $(filter-out 0 1,$(strip $(gb_DEBUGLEVEL))),\
    -DDEBUG_DOMAINMAPPER \
    -DDEBUG_ELEMENT \
    -DDEBUG_RESOLVE \
    -DDEBUG_CONTEXT_STACK \
    -DDEBUG_ATTRIBUTES \
    -DDEBUG_PROPERTIES \
    -DDEBUG_CONTEXT_HANDLER \
    -DDEBUG_IMPORT \
    -DDEBUG_LOGGING \
)
endef
gbuildize writerfilter 2011-04-14 05:35:11 -05:00			`define writerfilter_debug_flags`
better try. i feel exceptionally stupid today 2011-05-26 03:52:31 -05:00			`$(if $(filter-out 0 1,$(strip $(gb_DEBUGLEVEL))),\`
gbuildize writerfilter 2011-04-14 05:35:11 -05:00			`-DDEBUG_DOMAINMAPPER \`
			`-DDEBUG_ELEMENT \`
			`-DDEBUG_RESOLVE \`
			`-DDEBUG_CONTEXT_STACK \`
			`-DDEBUG_ATTRIBUTES \`
			`-DDEBUG_PROPERTIES \`
			`-DDEBUG_CONTEXT_HANDLER \`
			`-DDEBUG_IMPORT \`
dbglevel>1 should define DEBUG_LOGGING DEBUG_IMPORT enables code to open/close loggers, but DEBUG_LOGGING enables code to write to it, so having only one of the two in debug_setup.mk makes little sense. 2011-05-26 05:00:06 -05:00			`-DDEBUG_LOGGING \`
gbuildize writerfilter 2011-04-14 05:35:11 -05:00			`)`
			`endef`