From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: Antoine Cellerier <dionoea@videolan.org>
Cc: video4linux-list@redhat.com
Subject: Re: Announcing libv4l 0.3.1 aka "the vlc release"
Date: Sun, 29 Jun 2008 23:20:44 +0200 [thread overview]
Message-ID: <4867FCAC.8070607@hhs.nl> (raw)
In-Reply-To: <20080629210349.GA26587@chewa.net>
Antoine Cellerier wrote:
> On Sun, Jun 29, 2008, Hans de Goede wrote:
>> * Do not return an uninitialized variable as result code for GPICT
>> (fixes vlc, but see below)
>> * Add a patches directory which includes:
>> * vlc-0.8.6-libv4l1.patch, modify vlc's v4l1 plugin to directly call into
>> libv4l1, in the end we want all apps todo this as its better then
>> LD_PRELOAD tricks, but for vlc this is needed as vlc's plugin system
>> causes LD_PRELOAD to not work on symbols in the plugins
>
> You might want to submit those VLC specific patches upstream ...
A very valid point, and I will as soon as libv4l gets something resembling an
official release (as port of the v4l-dvb tree). I see that you are from
upstream. So what are your thoughts on this, is libv4l proven enough already to
submit patches?
The patches will probably need a couple of #ifdefs added to allow compilation
on systems without libv4l, right?
Regards,
Hans
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-06-29 21:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-29 20:41 Announcing libv4l 0.3.1 aka "the vlc release" Hans de Goede
2008-06-29 21:03 ` Antoine Cellerier
2008-06-29 21:20 ` Hans de Goede [this message]
2008-06-30 9:39 ` Gregor Jasny
2008-07-03 20:36 ` Gregor Jasny
2008-07-07 22:00 ` Hans de Goede
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=4867FCAC.8070607@hhs.nl \
--to=j.w.r.degoede@hhs.nl \
--cc=dionoea@videolan.org \
--cc=video4linux-list@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.