context switch

  GEN autogenerated.c
  CC file1.c
  CC file2.c
  LINK output
  INSTALL output

11 Comments »

RSS feed for comments on this post. TrackBack URI

1. it’s at least easy to get it to respect make -s:

   http://wednesdaynight.org/diary/2006/9/5

   i will leave the rest as an exercise for the reader.

   Comment by jacob berkman — Saturday, December 08 2007 #

2. I remember some project to do this a while back. A little searching later, and Google points me to http://kim.tensta.gannert.se/projects/pretty-am/

   Comment by Ori — Saturday, December 08 2007 #

3. Perhaps pretty-am can help you:

   http://kim.tensta.gannert.se/projects/pretty-am/

   Comment by foo — Saturday, December 08 2007 #

4. Maybe http://kim.tensta.gannert.se/projects/pretty-am/ ?

   It’s a bit outdated though; not sure if it still works with recent auto-foo..

   Comment by Peter Gordon — Saturday, December 08 2007 #

5. It’s mainly with automake; probably outdated now, but here’s how I did it.

   Comment by daniels — Saturday, December 08 2007 #

6. many thanks everyone for the link to pretty-am.

   I actually anted something like a m4 macro to ship with projects; will look at how pretty-am works and see if it can be used without patching automake directly instead.

   Comment by ebassi — Saturday, December 08 2007 #

7. @jacob

   thanks for the make -s support hack, sir.

   Comment by ebassi — Saturday, December 08 2007 #

8. Please don’t do this. You are creating a debugging nightmare for some poor soul down the road, who has to figure out why a build of your software failed catastrophically, on an automated system (e.g. Debian buildd network) which provides only limited information (just the make output; no forensic examination of failed build directories possible) and offers no direct access. A simple error in CFLAGS turns into a multi-hour or multi-day ordeal if you hide the commands.

   Comment by Zack Weinberg — Saturday, December 08 2007 #

9. @zack

   a “debugging nightmare”? I really can’t see why: the warnings and failures would still be reported as usual; the actual command line for compiling/generating/linking/installing a file would be the only think excised. it’s not like a >/dev/null 2>&1.

   and it would still be overridable anyway.

   Comment by ebassi — Sunday, December 09 2007 #

10. just to be precise, I want something like:

       CC clutter-actor.c
       Warning: compilation failed because of ${FOO}
    

    which is already available in the kernel, git and all the new GNOME Perl bindings, as it makes the debugging output actually readable for the people who needs to read it (developers and packagers).

    Comment by ebassi — Sunday, December 09 2007 #

11. I personnaly use pretty-am as well. Latest patch available works great (but has one little problem, some mv aren’t masked). I have to run a custom script to silent the extra libtool echo and thereafter compilation is all quieter and still shows errors like it should. A real pleasure to work with.

    Comment by Gilles Dartiguelongue — Sunday, December 09 2007 #

Leave a comment