Commit 1c8ece02 authored by Alessandro Rubini's avatar Alessandro Rubini

diag: allow VERB_LOG_MSGS to be set

There is no way to set VERB_LOG_MSGS. This Makefile change allows
to set USER_CFLAGS, for example like this:

   make USER_CFLAGS="-DVERB_LOG_MSGS -DCONFIG_PPSI_RUNTIME_VERBOSITY"

and then use "-V -V" to enable all messages.
Signed-off-by: Alessandro Rubini's avatarAlessandro Rubini <rubini@gnudd.com>
parent e53cb026
......@@ -8,6 +8,9 @@
# The default architecture is hosted GNU/Linux stuff
ARCH ?= gnu-linux
# Also, you can set USER_CFLAGS, like this (or on the command line)
# USER_CFLAGS = -DVERB_LOG_MSGS -DCONFIG_PPSI_RUNTIME_VERBOSITY
#### In theory, users should not change stuff below this line (but please read)
# classic cross-compilation tool-set
......@@ -28,6 +31,7 @@ TARGET = ppsi
all: $(TARGET).o
# CFLAGS to use. Both this Makefile (later) and app-makefile may grow CFLAGS
CFLAGS = $(USER_CFLAGS)
CFLAGS += -Wall -O2 -ggdb -Iinclude
# to avoid ifdef as much as possible, I use the kernel trick for OBJ variables
......@@ -51,11 +55,6 @@ ifdef PROTO_EXT
endif
include proto-standard/Makefile
# VERB_LOG_MSGS: uncomment if you want very verbose msg when log verbosity=2.
# As default, they are not even compiled, in order to save space in the final
# binary executable
# VERB_LOG_MSGS=y
# Include arch code
# we need this -I so <arch/arch.h> can be found
CFLAGS += -Iarch-$(ARCH)/include
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment