Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Building the Rockchip libv4l plugin
Date: Tue, 3 Jul 2018 22:37:43 +0200	[thread overview]
Message-ID: <20180703223743.447c9f7f@gmx.net> (raw)
In-Reply-To: <20180703033709.vkytmzcwaybt4wu7@tarshish>

Hello Baruch,

On Tue, 3 Jul 2018 06:37:09 +0300, Baruch Siach <baruch@tkos.co.il> wrote:

> Hi peter,
> 
> On Mon, Jul 02, 2018 at 09:16:35PM +0200, Peter Seiderer wrote:
> > On Mon, 2 Jul 2018 11:22:11 +0300, Baruch Siach <baruch@tkos.co.il> wrote:  
> > > I'm trying to build the Rockchip libv4l2 plugin in Buildroot. The source 
> > > is at
> > > 
> > >   https://chromium.googlesource.com/chromiumos/third_party/libv4lplugins/+/master/libv4l-rockchip_v2/
> > > 
> > > As upstream indicated[1], the code is meant to build as part of libv4l, not as 
> > > a standalone library. ChromiumOS sees to copy the code into the libv4l source 
> > > tree, and modify the relevant build configuration files[2].
> > > 
> > > What would be the best way to do that in Buildroot? A symlink to the plugin 
> > > source tree? Copy of the code to libv4l?  
> > 
> > ...or add a configure.ac/configure file to the source?  
> 
> Unfortunately the plugin really needs internal libv4l headers, so this is not 
> possible.

Something like the following (quick hack) patch, done the following first (should be added to libv4l):
 
	$ mkdir staging/usr/include/libv4l-1.14.2
	$ cp build/libv4l-1.14.2/config.h staging/usr/include/libv4l-1.14.2/

But failes with:

libv4l-encplugin-rockchip.c: In function ?ioctl_qbuf_locked?:
libv4l-encplugin-rockchip.c:392:8: error: ?struct v4l2_buffer? has no member named ?config_store?
  buffer->config_store = buffer->index + 1;
        ^~
libv4l-encplugin-rockchip.c: In function ?set_encoder_config_locked?:
libv4l-encplugin-rockchip.c:662:11: error: ?struct v4l2_ext_controls? has no member named ?config_store?
  ext_ctrls.config_store = buffer_index + 1;
           ^

Regards,
Peter

  reply	other threads:[~2018-07-03 20:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-02  8:22 [Buildroot] Building the Rockchip libv4l plugin Baruch Siach
2018-07-02  8:43 ` Nicolas Cavallari
2018-07-03  3:34   ` Baruch Siach
2018-07-02 19:16 ` Peter Seiderer
2018-07-03  3:37   ` Baruch Siach
2018-07-03 20:37     ` Peter Seiderer [this message]
2018-07-04  4:16       ` Baruch Siach

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=20180703223743.447c9f7f@gmx.net \
    --to=ps.report@gmx.net \
    --cc=buildroot@busybox.net \
    /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