From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Ariel D'Alessandro <ariel.dalessandro@collabora.com>,
linux-media@vger.kernel.org
Cc: hverkuil@xs4all.nl, sean@mess.org, p.zabel@pengutronix.de,
laurent.pinchart@ideasonboard.com, ezequiel@collabora.com,
nicolas@ndufresne.ca, kieran.bingham@ideasonboard.com,
gjasny@googlemail.com, xavier.claessens@collabora.com,
nicolas.dufresne@collabora.com, user.vdr@gmail.com,
sakari.ailus@iki.fi, mchehab+huawei@kernel.org, rosenp@gmail.com
Subject: Re: [v4l-utils v5 0/5] Add support for meson building
Date: Thu, 18 Nov 2021 11:03:59 +0200 [thread overview]
Message-ID: <db868d34-aaa5-7e89-59a5-a61e024b2ec9@ideasonboard.com> (raw)
In-Reply-To: <20210512184946.102863-1-ariel.dalessandro@collabora.com>
Hi,
On 12/05/2021 21:49, Ariel D'Alessandro wrote:
> Hi all,
>
> Another attempt to support meson build, addressing comments/fixes from
> reviewers.
>
> This patchset was developed on top of v4l-utils current master branch:
>
> commit f0c7e3d71eaf4182bae7eb3ee0e43b4eeb047ea9
> Author: Hans Verkuil <hverkuil-cisco@xs4all.nl>
>
> v4l2-ctl: add '--set-edid type=list' support
>
> You can find the patchset pushed to the following branch:
>
> https://gitlab.collabora.com/adalessandro/v4l-utils/-/tree/v4l-utils-meson-v5
>
> Feedback appreciated as always :-)
I was testing this (well, I'm using it, as I can't get the autoconf work with
cross-compilation..), and I see this problem if gconv is enabled when
cross-compiling for arm (buildroot system):
[1/2] Linking target contrib/gconv/EN300-468-TAB00.so
FAILED: contrib/gconv/EN300-468-TAB00.so
/home/tomba/work/buildroot/output32/host/bin/arm-buildroot-linux-gnueabihf-gcc -o contrib/gconv/EN300-468-TAB00.so contrib/gconv/EN300-468-TAB00.so.p/en300-468-tab00.c.o -Wl,--as-needed -Wl,--allow-shlib-undefined -shared -fPIC -Wl,-rpath,/usr/lib/x86_64-linux-gnu/gconv -Wl,-rpath-link,/usr/lib/x86_64-linux-gnu/gconv -Wl,--start-group /usr/lib/x86_64-linux-gnu/gconv/libJIS.so /usr/lib/x86_64-linux-gnu/gconv/libJISX0213.so -Wl,--end-group
/usr/lib/x86_64-linux-gnu/gconv/libJIS.so: file not recognized: file format not recognized
collect2: error: ld returned 1 exit status
[2/2] Linking target contrib/gconv/ARIB-STD-B24.so
FAILED: contrib/gconv/ARIB-STD-B24.so
/home/tomba/work/buildroot/output32/host/bin/arm-buildroot-linux-gnueabihf-gcc -o contrib/gconv/ARIB-STD-B24.so contrib/gconv/ARIB-STD-B24.so.p/arib-std-b24.c.o -Wl,--as-needed -Wl,--allow-shlib-undefined -shared -fPIC -Wl,-rpath,/usr/lib/x86_64-linux-gnu/gconv -Wl,-rpath-link,/usr/lib/x86_64-linux-gnu/gconv -Wl,--start-group /usr/lib/x86_64-linux-gnu/gconv/libJIS.so /usr/lib/x86_64-linux-gnu/gconv/libJISX0213.so -Wl,--end-group
/usr/lib/x86_64-linux-gnu/gconv/libJIS.so: file not recognized: file format not recognized
Also, would this be better, to be a bit more explicit:
- '-I.', # Needed for config.h
+ '-I' + meson.global_build_root(), # Needed for config.h
I would do the same to other ".." paths too, but maybe that's just a personal
preference:
-Icontrib/test/v4l2gl.p -Icontrib/test -I../contrib/test -I../lib/include -I../include -I.
I also wonder what the "-Icontrib/test" is for.
I also see a problem when cross-compiling where a wrong config.h is included. When
compiling with buildroot env, valgrind include dir is in the include paths. And valgrind
has a "config.h" there...
It would be safer to have the "-I." common flag before all the rest of the parameters,
instead of being after all the others, but I didn't immediately find out how to do
that with meson.
Tomi
next prev parent reply other threads:[~2021-11-18 9:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 18:49 [v4l-utils v5 0/5] Add support for meson building Ariel D'Alessandro
2021-05-12 18:49 ` [v4l-utils v5 1/5] Move README to markdown syntax Ariel D'Alessandro
2021-05-12 18:49 ` [v4l-utils v5 2/5] Add support for meson building Ariel D'Alessandro
2021-05-12 18:49 ` [v4l-utils v5 3/5] Copy Doxygen configuration file to doc/ Ariel D'Alessandro
2021-05-12 18:49 ` [v4l-utils v5 4/5] meson: Add support for doxygen documentation Ariel D'Alessandro
2021-05-12 18:49 ` [v4l-utils v5 5/5] Makefile.am: Distribute meson related files Ariel D'Alessandro
2021-05-13 8:56 ` [v4l-utils v5 0/5] Add support for meson building Kieran Bingham
2021-05-17 20:55 ` Ariel D'Alessandro
2021-05-17 22:13 ` Kieran Bingham
2021-05-18 7:23 ` Mauro Carvalho Chehab
2021-05-18 10:18 ` Kieran Bingham
2021-05-19 11:07 ` Mauro Carvalho Chehab
2021-06-16 13:36 ` Ariel D'Alessandro
2021-06-16 14:26 ` Ariel D'Alessandro
2021-06-16 14:59 ` Mauro Carvalho Chehab
2021-06-16 15:06 ` Xavier Claessens
2021-06-16 15:10 ` Nicolas Dufresne
2021-06-16 15:11 ` Laurent Pinchart
2021-10-04 14:24 ` Laurent Pinchart
2021-12-15 21:05 ` Laurent Pinchart
2021-11-18 9:03 ` Tomi Valkeinen [this message]
2021-11-18 10:09 ` Tomi Valkeinen
2021-12-15 21:07 ` Laurent Pinchart
2021-11-18 10:39 ` Laurent Pinchart
2021-12-15 21:10 ` 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=db868d34-aaa5-7e89-59a5-a61e024b2ec9@ideasonboard.com \
--to=tomi.valkeinen@ideasonboard.com \
--cc=ariel.dalessandro@collabora.com \
--cc=ezequiel@collabora.com \
--cc=gjasny@googlemail.com \
--cc=hverkuil@xs4all.nl \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=nicolas.dufresne@collabora.com \
--cc=nicolas@ndufresne.ca \
--cc=p.zabel@pengutronix.de \
--cc=rosenp@gmail.com \
--cc=sakari.ailus@iki.fi \
--cc=sean@mess.org \
--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