public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Video4Linux and linux headers
Date: Mon, 18 Apr 2005 02:07:55 +0200	[thread overview]
Message-ID: <200504180208.01297@enterprise.flameeyes.is-a-geek.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]

Hi,
I don't remember why I started looking at avifile this night, but while I was 
at it, I found something which uncovers a bit of troubles with v4l useflag.

Summarizing:

v4l useflag enables Video4Linux support (usually webcams and tv cards) on many 
multimedia softwares (like avifile, but not only).
As v4l is related to kernel, it needs kernel's headers to be used by software 
(usually linux/videodev.h file).
V4L is not avaiable on non-linux systems.

Now, I was trying to add dependency on headers if v4l was used, but adding a 
simple v4l? ( sys-kernel/linux-headers ) doesn't work as mips uses 
mips-headers.
I'm not sure to use virtual/os-headers as it targets also non-linux headers.

But then joem and geoman pointed out that v4l should only be used on linux, so 
it should be usemasked on other arches.

Now what? I'm going to ask here what to do with this. I think the right way 
should be adding v4l to base/use.mask and then -v4l on 
default-linux/use.mask, as it's strictly-linux thing.

-- 
Diego "Flameeyes" Pettenò
http://dev.gentoo.org/~flameeyes/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2005-04-18  0:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-18  0:07 Diego 'Flameeyes' Pettenò [this message]
2005-04-18  2:04 ` [gentoo-dev] Video4Linux and linux headers Mike Frysinger
2005-04-18  9:56   ` Diego 'Flameeyes' Pettenò
2005-04-18 18:27     ` Mike Frysinger
2005-04-19 19:57       ` Diego 'Flameeyes' Pettenò
2005-04-19 20:16         ` Mike Frysinger
2005-04-20 11:46           ` Diego 'Flameeyes' Pettenò
2005-04-20 12:20             ` Jan Kundrát
2005-04-19 23:06         ` Greg KH
2005-04-19 23:31           ` Mike Frysinger

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=200504180208.01297@enterprise.flameeyes.is-a-geek.org \
    --to=flameeyes@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox