All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: "Karicheri, Muralidharan" <m-karicheri2@ti.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: Help in adding documentation
Date: Wed, 18 Nov 2009 05:04:10 -0200	[thread overview]
Message-ID: <4B039C6A.8090907@infradead.org> (raw)
In-Reply-To: <A69FA2915331DC488A831521EAE36FE401559C5D80@dlee06.ent.ti.com>

Karicheri, Muralidharan escreveu:
> Mauro,
> 
> Thanks to your help, I could finish my documentation today.
> 
> But I have another issue with the v4l2-apps.
> 
> When I do make apps, it doesn't seem to build. I get the following error
> logs... Is this broken?

Well... no, it is not really broken, but the build system for v4l2-apps
needs serious improvements. There are some know issues on it:
	- It doesn't check/warn if you don't have all the dependencies
	  (qv4l2 and v4l2-sysfs-path require some development libraries
	   that aren't available per default when gcc is installed - I
	   think the other files there are ok);
	- make only works fine when calling on certain directories (it used to work
	  fine if you call it from /v4l2-apps/*) - but, since some patch, it now requires
	  that you call make from /v4l2-apps, in order to create v4l2-apps/include.
	  After having it created, make can be called from a /v4l2-apps subdir;
	- for some places (libv4l - maybe there are other places?), you need to
	  have the latest headers installed, as it doesn't use the one at the tree.
	- qv4l2 only compiles with qt3.

Patches are welcome to fix those issues and improve the v4l2-apps building system.

> make[3]: Entering directory `/local/mkaricheri/davinci_git/video_timing/new_v4l2-dvb/v4l-dvb-aba823ecaea6/v4l2-apps/libv4l'
> make -C libv4lconvert V4L2_LIB_VERSION=0.6.2-test all
> make[4]: Entering directory `/local/mkaricheri/davinci_git/video_timing/new_v4l2-dvb/v4l-dvb-aba823ecaea6/v4l2-apps/libv4l/libv4lconvert'
> cc -Wp,-MMD,"libv4lconvert.d",-MQ,"libv4lconvert.o",-MP -c -I../include -I../../../include -fvisibility=hidden -fPIC -DLIBDIR=\"/usr/local/lib\" -DLIBSUBDIR=\"libv4l\" -g -O1 -Wall -Wno-unused -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -o libv4lconvert.o libv4lconvert.c
> In file included from libv4lconvert.c:25:
> ../include/libv4lconvert.h:100: warning: "struct v4l2_frmsizeenum" declared inside parameter list
> ../include/libv4lconvert.h:100: warning: its scope is only this definition or declaration, which is probably not what you want
> ../include/libv4lconvert.h:105: warning: "struct v4l2_frmivalenum" declared inside parameter list

In this specific case, it is trying to compile against /usr/include/linux/videodev2.h, instead of using
the in-tree header file.

Cheers,
Mauro.

  reply	other threads:[~2009-11-18  7:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-17 16:00 Help in adding documentation Karicheri, Muralidharan
2009-11-17 16:28 ` Mauro Carvalho Chehab
2009-11-17 16:58   ` Karicheri, Muralidharan
2009-11-17 17:58     ` Mauro Carvalho Chehab
2009-11-17 23:29       ` Karicheri, Muralidharan
2009-11-18  7:04         ` Mauro Carvalho Chehab [this message]
2009-11-18  7:19           ` Hans Verkuil
2009-11-18  7:24             ` Mauro Carvalho Chehab
2009-11-18  7:32               ` Hans Verkuil
2009-11-19 16:23                 ` Karicheri, Muralidharan
2009-11-19 16:26                 ` Karicheri, Muralidharan
2009-11-19 17:01                   ` Karicheri, Muralidharan
2009-11-20 11:51                     ` Hans Verkuil
2009-11-18 18:19       ` Karicheri, Muralidharan
2009-11-18 19:47         ` Mauro Carvalho Chehab
2009-11-18 20:41           ` Karicheri, Muralidharan
  -- strict thread matches above, loose matches on Subject: below --
2009-11-17 15:57 Karicheri, Muralidharan

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=4B039C6A.8090907@infradead.org \
    --to=mchehab@infradead.org \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=m-karicheri2@ti.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.