Re: Prevent libtool-output

[Ralf Wildenhues]

Hi Thomas,

Please don't top-post, thanks.

* Roesner Thomas wrote on Fri, Sep 30, 2005 at 04:19:40PM CEST:
> * Ralf Wildenhues wrote:
> > * Roesner Thomas wrote on Fri, Sep 30, 2005 at 02:23:31PM CEST:
> > > 
> > > Can anybody tell me how to prevent the output of libtool while make is
> > > running?
> > > 
> > > I already put the --silent option for libtool in the Makefile.am, but I
> > > had no effort. Redirecting the output via >/dev/null is not suitable for
> > > the users.
> > 
> > Why?
> > 
> > > IMHO I need to put an @ in front of an command within the Makefile, if I
> > > want to suppress the output, and I've done so in a generated Makefile
> > > and it worked, but I think, that it is not the best way to change the
> > > generated Makefile`s
> > 
> > Currently >/dev/null is the best bet.  Implementing --quiet --quiet
> > (which will then be _really_ quiet) is on our TODO list.  If you have a
> > working patch, send mail to the libtool-patches list.  :-)


> it is because we cant see the useful information in on the first
> sight. The first Project has nearly 600 files of sourcecode, the
> second about 1000. There are some moments, we want/need to compile via
> console, not an ide.

Actually, I don't know what exactly you are referring to.
Do you want to avoid adding
  LIBTOOLFLAGS=--silent

to every Makefile.am?  Then just do
  make LIBTOOLFLAGS=--silent

which works with GNU make; for other make implementations, do
  env LIBTOOLFLAGS=--silent make -e

instead.  No need to recreate or change the Makefiles at all.

> Is there no m4 Macro or something like this used to create the
> according entry in the Makefile?

Hmm, maybe instead you would like this to be the default for the
package.  Then you can add
  AC_SUBST([AM_LIBTOOLFLAGS], [--silent])

to your configure.ac file(s) instead.

Does this help you?

Cheers,
Ralf