All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregor Jasny <gjasny@googlemail.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: v4l-utils migrated to autotools
Date: Wed, 18 Jan 2012 13:47:09 +0100	[thread overview]
Message-ID: <4F16BF4D.4070404@googlemail.com> (raw)
In-Reply-To: <4F16B8CC.3010503@redhat.com>

On 1/18/12 1:19 PM, Mauro Carvalho Chehab wrote:
> It would be nice to write at the INSTALL what dependencies are needed for
> the autotools to work, or, alternatively, to commit the files generated
> by the autoreconf -vfi magic spell there [1].

The end user gets a tarball created with "make dist" which contains all 
the m4 files.

For the developers I will list the dependencies (autotools-dev, 
pkgconfig and libtool) explicitely.

> Not sure if it is possible, but it would be great if the build output
> would be less verbose. libtool adds a lot of additional (generally useless)
> messages, with makes harder to see the compilation warnings in the
> middle of all those garbage.

I will add the AM_SILENT_RULES option later.

Thanks,
Gregor

  parent reply	other threads:[~2012-01-18 12:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-15 21:37 v4l-utils migrated to autotools Gregor Jasny
2012-01-17  8:21 ` Hans de Goede
2012-01-18 12:19 ` Mauro Carvalho Chehab
2012-01-18 12:31   ` Rémi Denis-Courmont
2012-01-18 12:43     ` Mauro Carvalho Chehab
2012-01-18 13:01       ` Rémi Denis-Courmont
2012-01-18 12:44     ` Patrick Boettcher
2012-01-18 12:56       ` Gregor Jasny
2012-01-18 13:02       ` Rémi Denis-Courmont
2012-01-18 12:47   ` Gregor Jasny [this message]
2012-01-18 12:54     ` Mauro Carvalho Chehab
2012-01-18 13:02       ` Gregor Jasny
2012-01-18 14:52         ` Mauro Carvalho Chehab
2012-01-18 16:42           ` Theodore Kilgore

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F16BF4D.4070404@googlemail.com \
    --to=gjasny@googlemail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.