All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Ezequiel Garcia <elezegarcia@gmail.com>
Cc: Gregor Jasny <gjasny@googlemail.com>,
	linux-media <linux-media@vger.kernel.org>
Subject: Re: [v4l-utils] Add configure option to allow qv4l2 disable
Date: Mon, 18 Jun 2012 19:01:12 -0300	[thread overview]
Message-ID: <4FDFA528.5020203@redhat.com> (raw)
In-Reply-To: <CALF0-+WpXzJi7Nh4yyjn-AToxFH04femQRf910J9PHNvqqex4Q@mail.gmail.com>

Em 31-05-2012 13:29, Ezequiel Garcia escreveu:
> Hi Gregor,
> 
> On Thu, May 31, 2012 at 4:07 AM, Gregor Jasny <gjasny@googlemail.com> wrote:
>> Hello,
>>
>>
>> On 5/30/12 3:42 PM, Ezequiel Garcia wrote:
>>>
>>> This patch could ease the job of a few people,
>>> by providing an option they actually need.
>>> OpenWRT [1] and Openembedded [2] are already disabling
>>> qv4l2 by applying ugly patches.
>>>
>>> [1]
>>> https://dev.openwrt.org/browser/packages/libs/libv4l/patches/004-disable-qv4l2.patch
>>> [2] http://patches.openembedded.org/patch/21469/
>>
>>
>> What's the purpose of this patch? As far as I can see it saves compile time
>> if Qt4 development stuff is installed. Otherwise building qv4l should be
>> skipped.
> 
> I just found that people were applying patches to disable qv4l2 compilation.
> In [2] you'll find this message: "The makefiles in the project attempt
> to use the hosts' compilers if
> qmake is installed." Perhaps, this was due to an old bug that's already solved.
> 
> So: I'm not sure if patch is useful, but I thought I could send it
> anyway and let you decide ;)

Yeah, compiling qv4l2 on embedded distros may be hard.
I'll apply it.

Regards,
Mauro

  reply	other threads:[~2012-06-18 22:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-30 13:42 [v4l-utils] Add configure option to allow qv4l2 disable Ezequiel Garcia
2012-05-31  7:07 ` Gregor Jasny
2012-05-31 16:29   ` Ezequiel Garcia
2012-06-18 22:01     ` Mauro Carvalho Chehab [this message]
2012-06-19 12:46       ` Ezequiel Garcia
2012-06-20 15:35         ` Gregor Jasny
2012-06-20 15:55           ` Mauro Carvalho Chehab

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=4FDFA528.5020203@redhat.com \
    --to=mchehab@redhat.com \
    --cc=elezegarcia@gmail.com \
    --cc=gjasny@googlemail.com \
    --cc=linux-media@vger.kernel.org \
    /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.