From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Gregor Jasny <gjasny@googlemail.com>
Cc: linux-media@vger.kernel.org, hverkuil@xs4all.nl,
kieran.bingham@ideasonboard.com, mchehab@kernel.org,
nicolas@ndufresne.ca, p.zabel@pengutronix.de, rosenp@gmail.com,
sakari.ailus@iki.fi, sean@mess.org, user.vdr@gmail.com,
xavier.claessens@collabora.com, deborah.brouwer@collabora.com,
ariel@vanguardiasur.com.ar, ezequiel@vanguardiasur.com.ar,
tomi.valkeinen@ideasonboard.com,
Ariel D'Alessandro <ariel.dalessandro@collabora.com>
Subject: Re: [v4l-utils] [PATCH v10 1/5] Add support for meson building
Date: Sun, 12 Mar 2023 16:49:03 +0200 [thread overview]
Message-ID: <20230312144903.GO2545@pendragon.ideasonboard.com> (raw)
In-Reply-To: <250e45e0-de13-5ef8-ce68-eb2cc9e58f73@googlemail.com>
Hi Gregor,
On Sun, Mar 12, 2023 at 03:31:29PM +0100, Gregor Jasny wrote:
> Hello,
>
> while packaging the v4l-utils master branch for the Ubuntu PPA[1] I
> noticed two issues:
>
> On 23.02.23 17:44, Laurent Pinchart wrote:
> > +dep_libbpf = dependency('bpf', required : get_option('bpf'), version : '>=0.7')
> > +if not dep_libbpf.found()
> > + dep_libbpf = cc.find_library('bpf', has_headers: 'bpf/bpf.h', required : get_option('bpf'))
> > +endif
>
> Ubuntu Jammy contains libbpf 1:0.5.0-1ubuntu22.04.1. Therefore the first
> dep_libbpf check fails due to the version constraint. But the second
> check for the header succeeds. Afterwards the build fails due to the too
> old libbpf.
>
> What's the reason for the fallback? I guess new enough versions of
> libbpf always ship a pkgconfig file.
autoconf didn't have any fallback as far as I can tell, so I think we
could drop it here too. As I can't easily test this on Ubuntu, would you
be able to send a patch ?
> > +git_sha = run_command(prog_git, '-C', meson.project_source_root(), 'rev-parse', '--short=12', 'HEAD',
> > + check : true).stdout().strip()
> > +conf.set('GIT_SHA', git_sha)
> > +git_commit_cnt = run_command(prog_git, '-C', meson.project_source_root(), 'rev-list', '--count', 'HEAD',
> > + check : true).stdout().strip()
> > +conf.set('GIT_COMMIT_CNT', '-' + git_commit_cnt)
> > +git_commit_date = run_command(prog_git, '-C', meson.project_source_root(), 'show', '--quiet',
> > + '--date=format-local:%F %T', '--format=%cd',
> > + env : ['TZ=UTC'], check : true).stdout().strip()
> > +conf.set('GIT_COMMIT_DATE', git_commit_date)
>
> In Debian / Ubuntu we built from a published tarball (created by meson
> dist). It does not contain a .git directory and therefore those checks fail.
>
> I created a patch to work-around the issue:
> https://git.launchpad.net/~libv4l/+git/v4l-utils-packaging/tree/patches/conditional-git-ops.diff
>
> But I'm not too fluent in Meson, yet.
You're doing quite fine :-) The patch looks good, except for
if fs.is_dir('.gitd')
which should be '.git' unless there's something I'm missing. Will you
submit the patch to the linux-media mailing list ?
> [1] https://code.launchpad.net/~libv4l/+recipe/v4l-utils-master
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2023-03-12 14:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 16:44 [v4l-utils] [PATCH v10 0/5] Switch build system to meson Laurent Pinchart
2023-02-23 16:44 ` [v4l-utils] [PATCH v10 1/5] Add support for meson building Laurent Pinchart
2023-03-12 14:31 ` Gregor Jasny
2023-03-12 14:49 ` Laurent Pinchart [this message]
2023-03-13 7:57 ` Gregor Jasny
2023-03-13 8:11 ` Laurent Pinchart
2023-03-14 7:03 ` Gregor Jasny
2023-03-18 18:17 ` Mauro Carvalho Chehab
2023-03-18 23:06 ` Laurent Pinchart
2023-03-19 0:20 ` Mauro Carvalho Chehab
2023-03-13 9:09 ` Sean Young
2023-03-13 10:15 ` Laurent Pinchart
2023-02-23 16:44 ` [v4l-utils] [PATCH v10 2/5] Copy Doxygen configuration file to doc/ Laurent Pinchart
2023-02-23 16:44 ` [v4l-utils] [PATCH v10 3/5] meson: Add support for doxygen documentation Laurent Pinchart
2023-03-20 11:38 ` Mauro Carvalho Chehab
2023-02-23 16:44 ` [v4l-utils] [PATCH v10 4/5] Drop autoconf/automake support Laurent Pinchart
2023-02-23 16:44 ` [v4l-utils] [PATCH v10 5/5] meson: Use -include to include config.h instead of -I Laurent Pinchart
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=20230312144903.GO2545@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=ariel.dalessandro@collabora.com \
--cc=ariel@vanguardiasur.com.ar \
--cc=deborah.brouwer@collabora.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=gjasny@googlemail.com \
--cc=hverkuil@xs4all.nl \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nicolas@ndufresne.ca \
--cc=p.zabel@pengutronix.de \
--cc=rosenp@gmail.com \
--cc=sakari.ailus@iki.fi \
--cc=sean@mess.org \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=user.vdr@gmail.com \
--cc=xavier.claessens@collabora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox