Hi! Some remarks on the CFLAGS thing: In one of my projects I used this approach for messing with CFLAGS: -- CFLAGS=-pthread CWARNFLAGS=-Wall -Wextra -Wshadow COPTFLAGS=-pipe -O2 CDEBUGFLAGS=-g -fstack-protector-all CFLAGS+=$(CWARNFLAGS) CFLAGS+=$(COPTFLAGS) #CFLAGS+=$(CDEBUGFLAGS) LDFLAGS=-lpthread -lrt -- It's somewhat GNU-makish, but you can easily switch CFLAGS by (un)commenting some of the "CFLAGS+=" lines. The linking rule then is "$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^"
So my CFLAGS are the absolute minimum required for a correct compile, and everything else are extras. And if you need "defines" they should go to CPPFLAGS. GNU makes built-in rules look like LINK.c = $(CC) $(CFLAGS) $(CPPFLAGS) $(LDFLAGS) $(TARGET_ARCH) PREPROCESS.S = $(CC) -E $(CPPFLAGS) COMPILE.c = $(CC) $(CFLAGS) $(CPPFLAGS) $(TARGET_ARCH) -c Maybe someone wants to restructure CFLAGS like that... Regards, Ulrich -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
