[Users] Re: [Devel] nicer compiling

Anand Kumria wildfire at progsoc.uts.edu.au
Wed Nov 30 19:16:04 CET 2005

Hi Bogdan,

On Tue, Nov 29, 2005 at 10:56:23PM +0200, Bogdan-Andrei Iancu wrote:
> Hi,
> thanks to Anand, you have now the liberty to get a more friendly output 
> during compilation. Just do:
>    NICER=1 make all

You also need to export either Q or NICER so that modules get compiled
with that flag too. I've attached a patch to do so.

> normal "make all" still produces same amount of output - it;s the 
> default since it's useful to see the compilation flags...at least for me...

Fair enough -- I normally find that the compilation lines cause warnings
and things to scroll past too fast.

That being said, I also do things like add in -Werror to stop
compilation dead in its tracks when I am developing.  In the attached
patch, this looks for a CVS directory and if found adds it in.


 `When any government, or any church for that matter, undertakes to say to
  its subjects, "This you may not read, this you must not see, this you are
  forbidden to know," the end result is tyranny and oppression no matter how
  holy the motives' -- Robert A Heinlein, "If this goes on --"
-------------- next part --------------
diff --git a/Makefile.defs b/Makefile.defs
index 2da1121..eb945d7 100644
--- a/Makefile.defs
+++ b/Makefile.defs
@@ -68,10 +68,9 @@ OSREL = $(shell uname -r)
 NICER ?= 
 ifneq ($(NICER),)
-	Q=@
+	export Q=@
 # TLS support
 TLS ?= 
 ifneq ($(TLS),)
@@ -905,6 +904,12 @@ endif
 endif #mode=release
+# during development, don't let errors in
+ISDEVEL=$(shell ls -d CVS 2>/dev/null)
+ifneq ($(ISDEVEL),)
+	CFLAGS+=-Werror
 #*FLAGS used for compiling the modules
 ifeq	($(CC_NAME), gcc)

More information about the Users mailing list